Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bloom-beacon!tut.cis.ohio-state.edu!unmvax!ncar!husc6!spdcc!ima!compilers-sender
From: henry@zoo.toronto.edu
Newsgroups: comp.compilers
Subject: Re: encripted source as an ANDF
Message-ID: <4003@ima.ima.isc.com>
Date: 31 May 89 09:11:04 GMT
Sender: compilers-sender@ima.ima.isc.com
Reply-To: henry@zoo.toronto.edu
Lines: 19
Approved: compilers@ima.UUCP
In-Reply-To: <3991@ima.ima.isc.com>

>> It seems to me that this kills any ANDF scheme which is not essentially
>> based on obfuscated (but non-preprocessed) source.
>
>In case you missed my point, I disagree very strongly.  You should be
>able to do a (partial) preprocessing step on the "development" system...

I should have been clearer.  Note the word "essentially", though.  I admit
I didn't think of partial preprocessing, which could be useful.

Do remember, though, that ANSI C in particular encourages rather more use
of macros with potentially implementation-specific bodies than older C
practice.  Not to say that partial preprocessing won't work, but a rather
larger number of identifiers are going to have to be marked "hands off".
[From henry@zoo.toronto.edu]
--
Send compilers articles to compilers@ima.isc.com or, perhaps, Levine@YALE.EDU
Plausible paths are { decvax | harvard | yale | bbn}!ima
Please send responses to the originator of the message -- I cannot forward
mail accidentally sent back to compilers.  Meta-mail to ima!compilers-request