A tale in 3 pictures.
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 Yesssss, goooood
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 @eniko Impressive!
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 @joe Hey, guess what syntax the C preprocessor strips out for you?
Guess what syntax is really common in web pages? (and also property lists, where I first encountered this clash)
-
@citizen428 @joe Hey, guess what syntax the C preprocessor strips out for you?
Guess what syntax is really common in web pages? (and also property lists, where I first encountered this clash)
@jrose @citizen428 to their credit, they did say it was a bad idea
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 @roskakori probably did this about 30 years ago
-
R relay@relay.publicsquare.global shared this topic
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 Himmel!
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 this is based actually
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 for GCC, add #define true 1
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 I suspect that the fact that my first reaction is "Oh, how do I get that?" says a lot about me. Probably not good things either.
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 This is magnificent and I *will* use it in production.
-
The horrors:
C preprocessor abuse
C preprocessor abuse. GitHub Gist: instantly share code, notes, and snippets.
Gist (gist.github.com)
So, it's some kind of chtml...
(you'll definitively want to put the ```#define HTML``` in a .h.tml file included by abuse.c)
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 *points and snaps* Nord Theme.
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 reminds me way way back in the late 1990s a long since defunct firm sold an e-commerce dev stack that they dubbed "WebC" that I recall was similarish concept—or crimes. Most definitely crimes.
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 The fact you can jump off the window isn't a good reason to do it. And don't mention someone brave who did: they're on the ground floor, stupid.
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 yes, that’s a thing I built my website on, at some point <https://aartaka.me/this-post-is-cpp.html> (migrated to ed(1) since then.)
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 ok, that’s a different kind of using
cpp(1)as a webpage templating engine than what I did.Won’t escape, of course…
-
The horrors:
C preprocessor abuse
C preprocessor abuse. GitHub Gist: instantly share code, notes, and snippets.
Gist (gist.github.com)
@citizen428 Glorious
-
A tale in 3 pictures. In which our hero wonders if he can and doesn't stop to ask if he should.
@citizen428 chef's kiss
-
@citizen428 reminds me of the horrors me and @friz64 were up to, also serving an entire web page from an ESP32 as one big string iirc, base64 encoded images and all.
@tea @citizen428 @friz64 reminded of tue gbs-control building a webpage into a byte array and spitting it out at runtime, as well as saving and loading files in a flash filesystem
and the gazillion associated race conditions
