Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!sdd.hp.com!ucsd!ogicse!oregon!jmeissen
From: jmeissen@oregon.oacis.org ( Staff OACIS)
Newsgroups: comp.sys.amiga.tech
Subject: Re: C compilers code generation
Message-ID: <68@oregon.oacis.org>
Date: 22 Nov 90 22:15:24 GMT
References: <dillon.7260@overload.Berkeley.CA.US> <1990Nov19.130657.19380@sisd.kodak.com> <90324.204949GIAMPAL@auvm.auvm.edu>
Organization: Oregon Advanced Computing Institute (OACIS)
Lines: 10

In article <90324.204949GIAMPAL@auvm.auvm.edu> GIAMPAL@auvm.auvm.edu writes:
>>#define SAY(s)  Write(backstdout, s, strlen(s))
>>which works for both SAY("const") and SAY(var).
>Yes this does work, but if the string is a constant, then you get a duplicate
>copy of the string put in your data segment.  I use :

Not if you are using SAS/Lattice :-) The Lattice compiler has an option that
will cause the compiler to only generate a single copy of duplicate string
constants (should be the default, IMHO. Isn't because of Unix wierdos who
modify string constants).