Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!iuvax!purdue!bu-cs!mirror!frog!john From: john@frog.UUCP (John Woods) Newsgroups: comp.sources.d Subject: Re: Comments on INSERT.c Summary: Use the SOURCE, Luke! Message-ID: <1354@X.UUCP> Date: 14 Jan 89 05:46:00 GMT References: <308@twwells.uucp> <313@twwells.uucp> Organization: Servants of the Great White Frog Lines: 22 In article <313@twwells.uucp>, bill@twwells.uucp (T. William Wells) writes: > : > 3) The unnecessary code sequences. The lseek's > The lseek's are completely unnecessary, regardless of omissions in > the man page. And of course, one should use standard I/O anyway. > I just checked the 3 Nov 87 draft of the ANSI C spec. I was astonished to find that they do not say what the value of the file pointer is after opening a pathname. Could someone with a recent copy check on this? The draft POSIX standard that I checked (12.3, the version of which was just short of being approved) DOES explicitly say that open() sets the file position to the beginning of the file. Frankly, I find the statement "..., regardless of omissions in the man page" offensive from someone complaining about coding style, as it smacks much too strongly of the "I read the source, I know what it REALLY does, and all the world's a VAX anyway" mentality. Probably that's not really what you feel, but that's how it reads. -- John Woods, Charles River Data Systems, Framingham MA, (508) 626-1101 ...!decvax!frog!john, john@frog.UUCP, ...!mit-eddie!jfw, jfw@eddie.mit.edu Go be a `traves wasswort. - Doug Gwyn