🚀 go-pugleaf

In article <90324.204949GIAMPAL@auvm.auvm.edu> GIAMPAL@auvm.auvm.edu writes:
   In article <1990Nov19.130657.19380@sisd.kodak.com>, jeh@sisd.kodak.com (Ed
   Hanway) says:
   >I'd never use strlen("constant") either, unless I knew that it was
   >evaluated at compile time. I have used (albeit in a toy program):
   >
   >#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 :

   #define MSG(s) { char *s; Write(Output(), s, strlen(s)); }

So use the flag on your compiler that forces identical string
constants into the same string. That way, you don't have the
extraneous variables (and manipulations thereof) in your code.

Or take the approach of one programmer I knew - he never coded string
constants, except for the place where he defined a variable to point
to them. But the compiler can do that for you.

	<mike
--
Cats will be cats and cats will be cool			Mike Meyer
Cats can be callous and cats can be cruel		mwm@relay.pa.dec.com
Cats will be cats, remember this words!			decwrl!mwm
Cats will be cats and cats eat birds.