Re: Multiple includes (was: Rob's going to hate me... (Remainder bug))
On Monday 10 November 2003 04:30 pm, Pete wrote:
> On Mon, 10 Nov 2003 17:12:53 +0000, Al Getz <Xaxo at aol.com> wrote:
> >include MyFile.e as MF
> >include MyFile.e as MyFile
> >
> >and now you can use either MF or MyFile to
> >access data in MyFile.e .
> >
> >This 'feature' cant be lost just because something else
> >is added, can it?
>
> Certainly not, I agree. Remember the lines may not be next to each
> other as shown, but at opposite ends of a large application, and it
> could be a real pain to ensure consistent namespaces across a large
> project, or be forced to edit third party source.
You read that wrong. We were talking about giving the same include two
different namespaces within a single source file. "Aliases", IOW.
This has nothing to do with what those namespaces are called in other files,
There's no reason you should have to edit other files or third party source.
You know this is true, because namespaces are never passed on.
Can show me a good reason to refer to one variable by two different names
within a single source file?
Irv
|
Not Categorized, Please Help
|
|
