Xref: utzoo comp.lang.c:23210 comp.lang.c++:5195 Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!cimshop!davidm From: cimshop!davidm@uunet.UU.NET (David S. Masterson) Newsgroups: comp.lang.c,comp.lang.c++ Subject: Re: A solution to the multiple inclusion problem Message-ID: Date: 24 Oct 89 16:56:58 GMT References: <14240@well.UUCP> Sender: davidm@cimshop.UUCP Distribution: comp Organization: Consilium Inc., Mountain View, California. Lines: 18 In-reply-to: nagle@well.UUCP's message of 23 Oct 89 16:34:49 GMT In article <14240@well.UUCP> nagle@well.UUCP (John Nagle) writes: (Many newer compilers do "#" processing in the same pass as main compilation, so referring to a "preprocessor" in this context is not necessarily correct.) I suppose that this is a performance enhancement and that now "#" processing is being considered so much a part of the language that compiler writers feel justified in doing this. However, doesn't this limit flexibility? Because of this, the problem being discussed results in having to change the compiler as opposed to changing the (probably more simple) preprocessor. -- =================================================================== David Masterson Consilium, Inc. uunet!cimshop!davidm Mt. View, CA 94043 =================================================================== "Nobody here but us chickens..."