Joshua Chamas schrieb:
Quoting Marko Friedemann <[EMAIL PROTECTED]>:
While we naturally use '#include file="2/B"' to include B from A, we also naturally use '#include file="C"' to include C from B. The problem is that this fails because it searches C in 1 rather than 2 due to the include simply not being aware of the fact that it was basically called from within 2. Calling B directly works, because ASP is then aware of being run in 2 and finds C accordingly.
While I personally consider this a bug, or a flaw at least, I would like to hear the opinion of you guys.
This is simply how it works, that the base directory includes are done from is first the directory of the executing script, followed by the Global directory and then any IncludesDir specified. This is really because the first directory searched is '.' and there has already been a chdir to that base directory of the executing script.
Well, yes. This IS how it works. The question is wether it is actually SUPPOSED to be that way and wether there is any security or whatever other reason for it to be so.
I did say that I consider this a flaw, because it is not what you usually want to do.
regards, Marko -- www.bmx-chemnitz.de -==- 20 Zoll in Chemnitz [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
