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

[David L. Nicol]

> >
> > I think this should be discussed a good amount. I think URIs are cool,
> > but too much trouble for simple stuff. I don't want to have to write
> > "file:///etc/motd" everytime I want to address a file. Too cumbersome.



Why not extend C<open> to be able to take other things besides
strings of text?  That way the strings of text still work and
don't work like they do now, files or processes, and the non-unix OSes
have to work with a little accent like an excellent professor born overseas,
(perhaps Andrei Codresceu but I degress) but the fileobject type, once
it is defined (all the fields in its packed pseudohash are filled, or
at least the ones that need to be), can be used insted of the file name string.

Strong typing means that that object isn't a string.