- Subject: Re: Re: Re: __FILE__ and path_rel
- From: Guenter Milde <milde@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 24 Jan 2003 13:03:27 +0100 (CET)
On Thu, 23 Jan 2003 23:01:11 +0100 wrote Klaus Schmid <klaus.schmid@xxxxxx>:
> > I.e. to translate a "Unix-convention" filename to the underlying
> > systems one?
> No. The superseded intention is to take advantage of organizing files
> within a directory tree and to use this structure for addressing files
> without assuming too much about this structure --> use relative file
> specifications. Do it system-independent and painless --> path_rel.
>
> Are you in doubt about the applications of path_rel?
> Should I describe more examples in more detail?
Problems:
assume windows: path_rel("c:\a\b", "e\..\f") == ??
assume windows: path_rel("c:\a\b", "e/../f") == ??
(BTW: what is the outcome of
expand_filename("a/b/../c")
under Windoof?)
Why not have a function
define __path__()
{
path_dirname(__FILE__);
}
and use this in your examples?
variable html_mode_path = __path__()
or
variable html_mode_path = path_concat(__path__(), "html");
?
Günter
--
Milde at ife.et.tu-dresden.de
--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.
[2003 date index]
[2003 thread index]
[Thread Prev] [Thread Next]
[Date Prev] [Date Next]