Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-Id: <200004030110.UAA11749@hp2.xraylith.wisc.edu> To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Permission denied with makeinfo from texinfo-4.0 In-reply-to: Your message of "Sun, 02 Apr 2000 20:46:34 EDT." <20000402204634 DOT D23469 AT cygnus DOT com> Date: Sun, 02 Apr 2000 20:10:17 -0500 From: Mumit Khan Christopher Faylor writes: > > Are we sure that this is a correct analysis? The previous analysis was > that ReadFile was being passed a length which was larger than its > supplied buffer. That is (to me) inarguably wrong. You can't say "I > know how big the file is" because you can *never* know how big the file > is in a multi-tasking operating system. > > It seems like Dave Bryan went to some effort to track this down and I don't > see that his analysis is incorrect. Dave's analysis is certainly correct, he's done a much more thorough analysis of the situation. I had obviously neglected to read through the entire thread, and missed some of the analysis. However, read IMO should not care whether I pass it a valid buffer or not if it's at end of file, and should return success and 0 bytes read instead. Doesn't excuse buggy code of course, but my reading of POSIX `read' requires this behaviour. Regards, Mumit