What I Wish I Had Known About Developing C/C++ From Linux Before I Started

Post by uninverted » Thu, Apr 23, 2009, 12:30 AM UTC

fix3r wrote: post #61

silentbicycle wrote: post #16

Earlier quoted context omitted.

The real issue is that C++ is too complicated and too slow to compile. Languages that are easier to throw together a reasonable parser for (Lisps, Smalltalk, Lua, or even C) have a much lower barrier to entry for development tools. Keeping the language syntax simple enough means that somebody scratching an itch can write something useful in an afternoon or a weekend, rather than taking a team and months.

Actually, no. The real issue is using compiler's front-end from the IDE itself. While it's true that C++ is hugely complex IDE writers shouldn't try to replace compilers (ie. trying as hard as they might they'll never get around C++ templates and their touring-completeness). MS got this right. gcc and every IDE that relies on it (like Xcode) is crippled in this regard.

Post by silentbicycle » Thu, Apr 23, 2009, 7:57 PM UTC

vorador wrote: post #102

silentbicycle wrote: post #89

Earlier quoted context omitted.

Have you ever used ed? Try to actually use it for a few and you'll get it. One good thing about ed is that it's always on even the most minimal system recovery disks (which often lack vi, even). I've been stuck using it a couple times while fixing dying systems. No fun, but better than nothing.

Actually I use a line-oriented text editor. I prefer using it because it makes me write shorter code, and I can't slack off five minutes because I'd forget the contents of the file.