home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!well!comeau
- From: comeau@csanta.attmail.com (Greg Comeau)
- Subject: Re: Version Strings...
- Message-ID: <C0KA0B.Jv0@well.sf.ca.us>
- Originator: comeau@well.sf.ca.us
- Sender: news@well.sf.ca.us
- Reply-To: comeau@csanta.attmail.com (Greg Comeau)
- Organization: Comeau Computing
- References: <1993Jan8.111612.25180@sunbim.be> <1993Jan8.145323.29380@samba.oit.unc.edu>
- Date: Sat, 9 Jan 1993 00:43:23 GMT
- Lines: 32
-
- In article <1993Jan8.145323.29380@samba.oit.unc.edu> Todd_Lewis@unc.edu (Todd M. Lewis) writes:
- >In article <1993Jan8.111612.25180@sunbim.be> accs1@bagheera.mumath writes:
- >>
- >>>UBYTE Version[] = "\0$VER: ProgName 1.0 (7.1.92)";
- >>
- >>I wonder why that stays in the executable. I would expect a good compiler
- >>would through that line away unless it is really referenced.
- >
- >....I'm not sure I would
- >call a compiler "good" if it started getting in the way building programs.
-
- Yes and no. This is one of those judegement call issues.
- I've seen this specific situation go either way. That is, OTOOH, it
- isn't referenced as far as the linker is concerned, so what good is it?
- OTOH, there are enough cases like I've seen over the years like Version
- or even trigger information for subsequent events in the compilations.
- Becomes like a question of when it smart dumb, and even when is smart
- being too smart.
-
- >Perhaps a "really good" compiler would have an option to turn off some
-
- >optimizations in selected places.
-
- That can help in some cases, but even that may not always be good
- enough. Especially in a different language.
-
- - Greg
- --
- Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418
- Producers of Comeau C++ 3.0 With Templates
- Here:attmail.com!csanta!comeau / BIX:comeau / CIS:72331,3421
- Voice:718-945-0009 / Fax:718-441-2310 / Prodigy: tshp50a
-