|FROM ||Ruben Safir
|SUBJECT ||Subject: [NYLXS - HANGOUT] (fwd) Re: C++ File Lokcing
|-- forwarded message --
From: Ruben Safir
Subject: Re: C++ File Lokcing
Date: Tue, 7 Jun 2011 18:50:50 +0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Content-Type: text/plain; charset=UTF-8
X-Trace: reader1.panix.com 1307472650 28210 18.104.22.168 (7 Jun 2011 18:50:50 GMT)
NNTP-Posting-Date: Tue, 7 Jun 2011 18:50:50 +0000 (UTC)
X-Blackjet: Blackjet is a Yankee Fan
X-DRMisTHEFT: Use GNU Linux today
X-From: A Dark Cloud
X-LOCATION: Brooklyn NY - Forget abou' it!
X-NYLXS: Really - yah think computers are supposed to be broken?
User-Agent: Pan/0.133 (House of Butterflies)
Xref: panix comp.lang.c++:1086202
> But Ruben, there is no such thing in C++ as "file descriptor". POSIX
> and C++ are orthogonal, not part of each other. On some systems there
> *may* be a way to get something from 'std::ios_base' other than what the
> Standard specifies, but it's *not* specified by the Standard, and that's
> why you need to *ask elsewhere*. Can you not see that?
Reading that other newsgroup for over a decade, I can tell you that
nobody there has the expertise in C++ to event shine your toe nail.
Talking to friends at Google, evidently they don't use ios base for file
access. They use unistd.h, fcntl.h, sys/file.h,
something is wrong, I'm not trolling, but it is fustrating me and
puzzles me too spend a month learning the details of a rather exotic
iostream class in C++ and then to find that it is all but useless because
you can't lock the files,
-- end of forwarded message --