1. Re: Modified Include System
Jason Gade wrote:
> I suggest that anyone who writes a file that is intended to be included use
> namespaces for files that *it* includes. Then it exports any functionality
> with
> it's own global routines if it needs to do that.
>
> Programmers cannot rely on moving a symbol over two levels of include files
> without the possibility of a namespace clash. Therefore this is the best
> workaround
> for something that is unlikely to be changed.
>
> Yes, it means that older or unmaintained libraries will have to be changed if
> someone runs into a naming conflict.
>
That doesn't solve the problem with files with the same name. Using namespaces
does not bypass the issue. Maybe you're talking about a whole different problem?
> j.
Regards,
Vincent
