News for hackers. Stuff that matters.
Re:Programmer Tooling Beyond Plain Text by coldtea on Wednesday May 06, 2015 @08:32AM (#9498112)
>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...

Re:Programmer Tooling Beyond Plain Text by ori_b on Wednesday May 06, 2015 @01:30PM (#9500316)
Are you suggesting that syntax errors create memory corruption?
Re:Programmer Tooling Beyond Plain Text by coldtea on Wednesday May 06, 2015 @04:18PM (#9501519)
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.

Re:Programmer Tooling Beyond Plain Text by ori_b on Wednesday May 06, 2015 @05:15PM (#9501860)
Those are semantic errors, and a language aware editor will not fix them.
Re:Programmer Tooling Beyond Plain Text by xj9 on Wednesday May 06, 2015 @11:09AM (#9499201)
That sounds like a language problem, not an editor problem.