From: billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu (William Thomas Wolfe, 2847 )
Subject: Re: Tucker's new proposal
Date: 22 Dec 89 20:39:12 GMT [thread overview]
Message-ID: <7518@hubcap.clemson.edu> (raw)
In-Reply-To: 20600028@inmet
From stt@inmet.inmet.com:
> I *can* imagine a careful definition of conditional
> compilation mechanisms which would preserve the ability to
> recompile from parse trees. This would *not* be a preprocessor
> approach, however. [...]
%
% Allow if constructs and case constructs within a sequence of
% declarations, so long as all conditional and case
% expressions are static, and each if/case "arm" contains
% only declarations (rather than statements).
%
> The nice thing about this kind of approach is that it builds on the
> existing concepts of the language (namely static expressions,
> if/case constructs, and variant records), rather than introducing
> a new/foreign syntax like "#ifdef".
I must be getting a bit too much of the spiked eggnog myself,
because this is actually starting to sound like not too bad an
idea... can anyone think of counterarguments?
Bill Wolfe, wtwolfe@hubcap.clemson.edu
next prev parent reply other threads:[~1989-12-22 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <629648260@<1825>
1989-12-18 19:09 ` 9X and the NEED for preprocessing stt
1989-12-19 21:29 ` preprocessing & optimization William Thomas Wolfe, 2847
1989-12-21 20:58 ` stt
1989-12-22 20:39 ` William Thomas Wolfe, 2847 [this message]
1989-12-30 5:22 ` Tucker's new proposal Metafont Consultant Account
1989-12-19 22:12 ` 9X and the NEED for preprocessing arny.b.engelson
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox