Silly C++ formatting of error messages.

[Mo McKinlay]

# > @<filename>
# 
# Just like VC++?  :-)

I was thinking of BC++, but the same applies ;-)
 
# I use the -specs=foo option for things like this, when I want to pass
# additional parameters.  Put the additional flags in the local 'foo'
# file (the trick is getting the specs file format exactly right; it is
# not meant to be used directly by humans like this).  This helps with
# the max command-line length problem.

I hadn't thought of the -specs= option - I've not really dealt with specs
at all - mainly because, as you say, they're not exactly user-friendly.
Running into an ICE because of a scewed up specs file is a little too easy
to make them useful for general use, IMHO.
 
# Files like .gccrc that take effect magically and silently open up a can
# of worms like you said, and MHO is that it's more trouble than it's worth.

I'd have to agree there. A user-specifiable one would be useful, though -
i.e., it has to be explicitly requested on the command-line.

-- 
Mo McKinlay             Chief Software Architect              inter/open
mmckinlay@labs.interopen.org                    http://www.interopen.org