Re: RFC 14 (v3) Modify open() to support FileObjects and

>>>>> "JSD" == Jonathan Scott Duff <[email protected]> writes:

JSD> I originally didn't like this but the more I think about it, the more
JSD> I like it ... as long as the default handler knows about URIs :-)

JSD> I'd like 
JSD> 	open "http://www.perl.com";
JSD> do DWIM.  

(Some random thoughts.)

What hasn't been discussed, is 

Are files (or perhaps resources) named natively or in a portable fashion?

If portable, then
	for (@ARGV) { open $_; ... }
has to DWIM both portable and native formats.

If native, then the URI has problems.


There also comes the overhead (programming effort) of converting
_some_ resource names to native format for output to the user.
And deciding which of those resource names should be transformed
will be tough.

And how does one open sockets or connections to custom servers?

Will open take over the work of socket() and family? What is the
resource supposed to look like?

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