"John D. Leonard II" wrote:
>
> Mike:
>
> I believe that documents are compiled into packages whose namespace is
> constructed from their file name. If the file name is similar (even if the
> desired behavior is to load them from a different directory) the one in
> memory is used first. This similarity will often occur because the files
> are loaded from the @INC, the Global directory, or because their package
> names are build from a relative rather than absolute file name.
>
> SOLUTION:
>
> $Response->Include( $Server->MapPath("./header.asp") );
>
>
This is a good work around, but perhaps this needs to be treated
as a bug. Its seems reasonable that if you are in different
parts of an application, defined by a shared Global setting, but
just in different directories, that each should be able to include
a separate header.inc.
What was defeating this was the notion of '.' for the first directory,
which when later used for as part of the file name parsed into
a subroutine name would give you something like $GlobalPackage::__header_asp
regardless of where you included it from.
To fix, this I'll try to have not '.' for the first directory
in the search path, but rather dirname($0), or the directory
the current script is in.
I'll try this in my dev version, and send it to you John when
its ready.
--Josh
_________________________________________________________________
Joshua Chamas Chamas Enterprises Inc.
NodeWorks Founder Huntington Beach, CA USA
http://www.nodeworks.com 1-714-625-4051
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
