[coldtea]

>Once out of the newb phase. Once I've fully grokked the language and I've had enough ramp-up that I'm in "the zone" it's nearly effortless to type syntax-perfect code on my 1st attempt. Even getting built-in library calls and macros right, on 1st attempt, becomes nearly effortless, once in that frame of mind.

And yet, it's this "nearly" that creates all the huge C buffer overflow and memory corruption bugs...

[ori_b]

Are you suggesting that syntax errors create memory corruption?

[coldtea]

Quoting: "even getting built-in library calls and macros right, on 1st attempt, becomes nearly effortless"...

Getting the syntax to parse != getting the correct syntax (meant for the job).

Even an off by one error in a library call can create memory corruption. Preprocessor macros? They can fuck everything if done wrongly.

[ori_b]

Those are semantic errors, and a language aware editor will not fix them.

[xj9]

That sounds like a language problem, not an editor problem.