On Sun, Oct 08, 2000 at 12:39:37PM +0000, neil wrote:
> The problem comes when you have intermediate parent directories (i.e.
> between the current directory and the website root) which may or may not
> have 'file.html' defined - this means that you have to redefine file.html
> all the way up the hierarchy (each one perhaps just calling its parent),
> which clutters up the directories.
Ok, thanks, I see your point now. I agree with you that this
would be a nice feature.
> The other point was that multiple calls of the form Execute('../file.html')
> >from the same hierarchy will not work, as Embperl apparently uses the
> literal filename which is supplied to Execute() to uniquely identify the
> file in the cache. To workaround this I currently have to make a special
> symbolic link in each of my directories, which links to the immediate
> parent directory. I name the link according to what the current directory
> is. So, if I am in a directory called foo, then I make a link called foo..
> which points to the parent (..). Now, to call the parent file.html from
> within foo/file.html, I use Execute ('foo../file.html').
I think I see your point here, too. And again I agree that it
should be that way. Well, let's wait and see what Gerald thinks
about this ;-)
Andre
--
/"\
\ /
X ASCII Ribbon campaign against HTML E-Mail
/ \
PGP signature
