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

[Chaim Frenkel]

>>>>> "JH" == Jarkko Hietaniemi <[EMAIL PROTECTED]> writes:

>> Please explain why internally it needs to be represented as anything 
>> other than what the user passed in.

JH> A flat string is a pain to handle because then you have to know
JH> in which platform it was originally created: what semantics does
JH> it obey, how to parse it.

I don't see how your proposal solves the problem. It still has to
know what the source/intended/target platform is.

Why do all those acts have to be performed to do an open?

Hmm, unless you are planning to have a direct perl <-> os layer. 
(A rewrite/stealing^wborrowing from sfio?)

<chaim>
-- 
Chaim Frenkel                                        Nonlinear Knowledge, Inc.
[EMAIL PROTECTED]                                               +1-718-236-0183