Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!uc!cs.umn.edu!!jdege
From: jdege@ (Jeff Dege)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice/SAS C  5.10 HERE!
Message-ID: <1990Aug24.174645.15969@cs.umn.edu>
Date: 24 Aug 90 17:46:45 GMT
References: <14874@shlump.nac.dec.com> <1990Aug24.060138.2233@ariel.unm.edu>
Sender: iacovou@cs.umn.edu (Danny Iacovou)
Reply-To: jdege@donald.UUCP (Jeff Dege)
Organization: University of Minnesota, Minneapolis
Lines: 24

In article <1990Aug24.060138.2233@ariel.unm.edu> sdowdy@carina.unm.edu.UUCP (Stephen Dowdy) writes:
>In article <14874@shlump.nac.dec.com> barrett@meridn.enet.dec.com
>
>Woah!!!
>I don't recall anywhere where it says "#define lines should adhere to
>ancient FORTRAN coding practices".  Admittedly, I'd never write a 30 line
>#define, but it is not too much to expect software not able to deal with
>such excess to at least abort with an error, or truncation of the directive.
>
   Howabout:
 
#define DPRINT(type, var)        \
{                                \
char buf[80];                    \
sprintf(buf, "%s = %" type; #var, var); \
msg_disp(buf);                          \
}
/* usage is DPRINT(d,intvar);, and msg_disp() displays a string in a window
in a system-friendly way. */
 
Extending this sort of thing soon leads to fairly long #defines.

-----------------------------------------
......................................