httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject RE: Ugh. canonical pain for OS2
Date Thu, 19 Oct 2000 14:59:08 GMT
> From: Brian Havard []
> Sent: Thursday, October 19, 2000 5:20 AM
> >Since canonical_name in Unix is a noop (relative remains relative)
> >and Win32 retains relative paths, I'm afraid we aught to consider
> >the draconian measure of applying this patch and expecting OS2 to
> >keep up.  I realize this isn't terribly fair to you, Brian :-(
> >
> >So what are your thoughts, given this situation?  Do we go back
> >to accepting "\" in ap_os_is_path_absolute?  I'm certain that isn't
> >what we want.
> I'd argue that any relative path isn't canonical as its meaning varies with
> the cwd. The correct fix should be to make ap_os_is_path_absolute() work.
> ap_os_canonical_filename() != ap_convert_backslashes_to_forward_slashes().

  ap_os_canonical_filename != ap_make_fullpath, either.

I'd reckon you are philisophically right, which is why I strongly believe
this function always has been misnamed.  I'd agree it is also more complex 
than s|\|/|.  That doesn't change the fact that it is not absolute, and we
have a function that should do so.  Any other solution breaks compatibility
and trust between os2 and unix.

View raw message