How to C

https://matt.sh/howto-c

Very good read for anyone that wants to write this outdated language in 2016.

Do you even read English? Does using one word vs another even mean anything to you? You can't even respond to what I say.

mangled C macro

Totally doable in Lisp, and I explained the process to getting there. Desire for behavior → C fucks it up with weak-ass preprocessor shit → Unfuck it back to behavior → Nice Lisp macro that isn't a shit hack but does the same thing better. If I took the time to unmangle it, I would likely follow the same idioms in Lisp.

Fuck, I can implement the whole fucking C preprocessor in Lisp's macro system, just to shut you the fuck up about your shitty weak string masher.

No other Pascal dialect is C/C++ independent.

Pascal is a language that is not dependent on C, which is a completely different language, as you don't seem to know the distinction. Which part of the Pascal language depends on the C langauge? Be clear and specific, you laughably stupid piece of shit, or shut the fuck up and kill yourself.

Only in a contrived, virtual environment written in C/C++/asm.

Lisp takes my Lisp and converts it to machine code. You're contriving C into the picture because you're a desparate loser who can't admit that the old shit you've never learned past is being laughed at.

it patently obvious C and C++ have no signs of dying or being replaced.

Who even teaches C anymore in universities? Not that Java doesn't suck, but it's at the very least left common CS curriculum. Such is the way to becoming the next Cobol.

[popularity]

I know you can't read, but "is popular" ≠ "growing in popularity" anyway.

The era is gone

Again, because top popularity is driven by money, politics, and momentum. Which speaks nothing about the power, flexibility, ease of use, and speed of a language.

I don't need to be a chef to comment on taste of food.

You've never even tasted Lisp enough to make a determination. Reading between the lines, it's like you think it's still interpreted or something.

It's not fast

What the fuck are you smoking? Even just looking at the very first benchmark:

C:
secs N KB gz cpu cpu load
binary-trees 0.09 12 ? 706 0.07 0% 30% 80% 0%
binary-trees 1.61 16 9,492 706 1.60 100% 1% 2% 1%
binary-trees 37.71 20 132,384 706 37.68

Lisp:
secs N KB gz cpu cpu load
binary-trees 0.07 12 ? 612 0.06 100% 0% 0% 0%
binary-trees 1.36 16 77,168 612 1.35 1% 1% 1% 100%
binary-trees 32.77 20 325,092 612 32.71

Going down the line, Lisp takes the advantage often enough. Certainly it's competitive with C, thus "one of the fastest languages" would be apt for that competitiveness.

But this doesn't even begin to describe the speed advantages in the "real world", with large-scale programs where it actually counts. C gets slow when you use it in real systems, because it needs to dispatch, change runtime behavior based on user scripts/config/data, track shit that it doesn't know the lifetime of. Pull it into real world large scale and your C code is buggier, slower at runtime, and harder to write than Lisp, while dynamic runtimes eat those problems for breakfast.

Now, show me some fucking working roman numerals.