Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

GCC is BLOATED

Name: RMS Matthew Stallman 2010-11-29 19:42

g++ -o foo bar.cpp creates a 7kb executable

which would be cool if bar.cpp didn't consist of:

int main(){}

Fuck this shit. Is there some sort of compiler flag I'm missing out on, or is my anus totally haxxed?

Name: Anonymous 2010-11-30 15:23

>>24
Yes, of course.

* It's not like I have any constraints re: vertical space. Actually, when I do want to see as much lines as possible simultaneously it's because I have used some commands producing a lot of output, and having a distinct line separating those commands is clearly beneficial, while the relative area of the prompt is all but insignificant.

* I do have constraints re: horizontal space sometimes, so having an actual prompt line as short as reasonably possible (two characters) is clearly beneficial again. Also, it's nice if the commands are more or less aligned with their output. And with each other, if your prompts might be differing.

* Which brings me to my last point: I have like ten environments for compiling shit only, with usually tree or four opened simultaneously. I really, REALLY don't want to do some stuff in the wrong place, or to compulsively check where I am all the time, I want the warm feeling of having that information in my not so peripheral vision at all times. Since there are no real drawbacks to it, I do.

In more accessible to yourself terms: it's like a HUD in your Call of Warfare -- yeah, sure, it takes some screen space, but its usefulness far outweighs the price.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List