Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!udel!rochester!kodak!sisd!jeh
From: jeh@sisd.kodak.com (Ed Hanway)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice/SAS C  5.10 HERE!
Message-ID: <1990Aug24.192840.27668@sisd.kodak.com>
Date: 24 Aug 90 19:28:40 GMT
References: <14874@shlump.nac.dec.com>
Sender: news@sisd.kodak.com
Organization: Printer Products Division Eastman Kodak
Lines: 22

In article <14874@shlump.nac.dec.com> barrett@meridn.enet.dec.com (Keith Barrett) writes:
>In article <1990Aug23.052447.24545@zorch.SF-Bay.ORG>, xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) writes...
>>So tell me, does it still do a no-warning, no guru, stone cold system
>>crash, trashing Rad:, if you try to do/use a 30 line #define?
>
>Standard C coding practice recommends that a define should fit in 1 line
>of 80 characters; I think you got what you deserved.

Overflowing a compiler limit might deserve an error message, but certainly
not a system crash.

Start doing stuff like

#define putrgb(x) do { putchar((x).r); putchar((x).g); putchar((x).b)} while(0)

and you can run up against preprocessor limits in a hurry. On the sun I'm
using to enter this message, "putrgb(a_big_struct_name->member)" expands to
about 1350 characters.

Kudos to Lattice, er, SAS for finally allowing the limit to be expanded.

Ed