My recollection -- and this may no longer be the case -- is that
fixed-length records can be altered and re-written in place, but
variable-length records must exactly match in length, new record to
old, or the remainder of the file is forfeit (made null).
-R.
On 2011-04-26 00:20, Glenn Knickerbocker wrote:
On 04/25/2011 10:20 PM, Paul Gilmartin wrote:
From the point of view of the programmer coding to the API (Pipelines
in this context), it may well be satisfactory "if it hides the fact."
Right, I'm much more interested in *MY* not having to read and alter the
existing record than in what some system-level call has to do--though of
course saving real resources never hurts either!
block (except for filemode number 6, and that's very special purpose,
and has severe restrictions that I'd call bugs).
You've piqued my curiosity. I've used mode 6 for decades to avoid
errors in reading and writing simultaneously. Am I just accepting
quirks you don't, or have I missed some restrictions?
¬R
--
Regards, Rod Dav4is / P.O. Box 118 / Hyde Park, NY 12538 / USA
Genealogy, et Cetera: http://freepages.rootsweb.ancestry.com/~dav4is/
538 ancestral& collateral families, mostly 17°-19° century
New England& European roots. Total population: 136,000+
Annex: http://www.gencircles.com/users/dav4is/
email: dav...@yahoo.com
A Democrat, a Republican and a giraffe walk into a bar. The bartender looks up from his
want ads and says, "What is this, a joke?"
-unknown
