Newsgroups: comp.lang.c++
Path: utzoo!henry
From: henry@zoo.toronto.edu (Henry Spencer)
Subject: Re: comp.lang.c++, rms, and software patents
Message-ID: <1990Dec15.235642.10008@zoo.toronto.edu>
Organization: U of Toronto Zoology
References: <BURLEY.90Dec14121748@pogo.ai.mit.edu>
Date: Sat, 15 Dec 90 23:56:42 GMT

In article <BURLEY.90Dec14121748@pogo.ai.mit.edu> burley@pogo.ai.mit.edu (Craig Burley) writes:
>Clearly, if #include requires a license, then C++ (and C) will have to be
>changed to incorporate a new mechanism that replaces most or all of the
>functional capabilities of #include without using textual inclusion...

No, the languages can stay the same.  Only the implementations would have
to change.  There is no reason not to use #include to signify invocation
of the new mechanism.  Indeed, ANSI C does not actually guarantee that, say,
`#include <stdio.h>' is implemented by textual inclusion.
-- 
"The average pointer, statistically,    |Henry Spencer at U of Toronto Zoology
points somewhere in X." -Hugh Redelmeier| henry@zoo.toronto.edu   utzoo!henry
