Fw: gcc 3.2 code bloating?

[Miguel Ramírez]

> MinGW links the SC++L and support libraries statically, while I'm
> pretty sure that most Linux installations out there links them
> dynamically. This is the main culprit of the difference.
>
> OTOH, using toy programs to check if a compiler produces bloated
> executables is... well... not very scientific.
>

I was not trying to be 'scientific' neither tried to do some kind of
proof. I was just shocked and asked for some ideas about what
seemed to be a problem. Since
English is not my mother tongue and e-mails aren't able to express
all the nuances of sponken English ( or Spanish ) I apologize if
someone misunderstood my question.

> > My training as programmer has conditioned me to think about big
> > executables as generally evil ( bigger process = slower context
> > switching ).
>
> My _experience_ as a programmer tells me that, on almost all cases,
> the overhead introduced by large executable code is negligible
> compared against other factors. You'll better care about your
> algorithms and general design.
>

That's always true. Also is true that large-scale software developing  can
be
sometimes defined as 'caring about the details'. Unbound variables are
software
developers nemesis, either they are expressed in code or in some other, more
subtle and often perverse, form (ask JPL guys).