RE: Null filename ("") is considered to correspond to an existing, readable, and writable file?

[Drew Adams]

    > Those general design goals are fine, but they
    > don't speak specifically to the advantage of _this_ 
    > particular design. They don't, for example, show an
    > advantage over considering "" to not be a file
    > name (neither relative nor absolute).
    
    One advantage, IMO, is that no error is thrown or signaled for "",
    which means application code will not need to cope with these
    exceptional situations.

OK. Thanks.