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

>>>>> "JH" == Jarkko Hietaniemi <[email protected]> writes:

JH> I agree with Dan: people do seem to get into "have to" mode awfully
JH> soon and easily.  The proposed framework is supposed to make it easy
JH> to handle file names and make Perl internals (well, not internal-
JH> internals, but the IO layer) better support multiplatform situations,
JH> both when scripts have to run on multiple platforms, and when
JH> an application is running on multiple platforms _simultaneously_,
JH> servers-clients, peers-peers, etc.

Fine. Then all the 'parts' of a generic filename (or should that be
a resource name) are pure strings?

Who supplies the logic to scrunch them together into an understandable
(to the os) form?

And how do we make it easy to pass in a name to open?

	$fh = open Perl::Canonical(Host=>"remote"
				    ,OS=>"VMS"
				    ,Device=> "DAO"
				    ,Path=>("path", "to", "resource")
				    ,Name=> "filename"
				    ,Type=>"txt"
				    ,Version=> ":oldest"
				);


Seems messy.

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