Re: Internal Filename Representations (was Re: Summary of I/O related RFCs)

On Sun, Aug 13, 2000 at 01:22:30PM -0400, Chaim Frenkel wrote:
> >>>>> "JH" == Jarkko Hietaniemi <[email protected]> writes:
> 
> JH> On Sun, Aug 13, 2000 at 09:40:07AM -0400, Bryan C. Warnock wrote:
> >> This all seems like a lot of work for (what I would consider to be) the
> 
> JH> Read carefully the subject: *internal* representation.  If you are
> JH> opening a file with open() or sysopen(), you supply a string with your
> JH> native FS semantics and think no more of it.
> 
> What RFC? I couldn't find it on http://dev.perl.org/rfc/
> 
> Please explain why internally it needs to be represented as anything 
> other than what the user passed in.

(Once I get around updating the RFC) I will also refer to Tcl's way:

http://dev.scriptics.com/man/tcl8.4/TclCmd/file.htm

Take a look e.g. at the 'file split' and 'file join' commands,
and also the 'filename', which says this:

: However, scripts that are intended to be portable should not assume a
: particular form for file names. Instead, portable scripts must use the
: file split and file join commands to manipulate file names (see the
: file manual entry for more details).
 
-- 
$jhi++; # http://www.iki.fi/jhi/
        # There is this special biologist word we use for 'stable'.
        # It is 'dead'. -- Jack Cohen