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

[Eli Zaretskii]

> From: "Drew Adams" <address@hidden>
> Date: Tue, 3 Jan 2006 10:51:11 -0800
> 
> My question was stated carefully in terms of "all file-name arguments to
> functions", but you misread it as "all files" or perhaps "all file names".

If that is the misreading, then I'd say it's not a misreading at all:
since file-name arguments _are_supposed_to_be_ file names, it is only
natural to assume it's clear to the reader that what applies to file
names applies also to the file-name arguments of file-related
functions.