Sujet : Re: encapsulating directory operations
De : mutazilah (at) *nospam* gmail.com (Paul Edwards)
Groupes : comp.lang.cDate : 21. May 2025, 11:44:12
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <100kaq0$2q1v3$1@dont-email.me>
References : 1 2 3
User-Agent : Microsoft Outlook Express 6.00.2800.1106
"Keith Thompson" <Keith.S.Thompson+
u@gmail.com> wrote in message
news:87h61ezf76.fsf@nosuchdomain.example.com...It looks like it treats a directory as a file containing a
sequence of *lines*, each of which is a file name. The problem
with that is that on some systems, file names can legally include
newline characters. I don't suggest it's not a horrible idea to
take advantage of that, but it is something that would have to be
addressed in a language standard.
And - that's part of my question.
The language standard would need to say something along
the lines of "if any filenames contain a NL character, the
results are implementation-defined".
Any issue with that?
Not sure if there is any careful wording needed because people
have VMS in their minds (obviously they don't literally write
VMS in the standard - but it may appear in the Rationale).
Ditto MVS would be the reason why mkdir() can't be
implemented - and mentioned in the Rationale, not the Standard.
BFN. Paul.