Add Proposal | Add Analysis | Edit Class, Environment, or Release |
Number | 80
|
Category | errata
|
Synopsis | 17.2.7 omits description of use of fd
|
State | open
|
Class | errata-simple
|
Arrival-Date | Jul 29 2002
|
Originator | Daryl.Stewart@cl.cam.ac.uk
|
Release | 2001b, 17.2.7
|
Environment |
|
Description |
17.2.7 $ferror does not explain use of "fd" argument. $ferror returns error status of last operation on fd. Change description to: A string description of the error encountered by the most recent file I/O operation on file descriptor fd is written into the reg str which should be at least 640 bits wide. The integral value of the error code is returned in errno. If the most recent operation on file descriptor fd did not result in an error, then the value returned shall be zero, and the reg str shall be cleared. |
Fix |
|
Audit-Trail |
From: Daryl Stewart <Daryl.Stewart@cl.cam.ac.uk> To: Shalom.Bresticker@motorola.com Cc: etf-bugs-direct@boyd.com, Daryl.Stewart@cl.cam.ac.uk Subject: Re: errata/80: 17.2.7 omits description of use of fd Date: Mon, 29 Jul 2002 11:26:01 +0100 Should something be said about using $ferror after $fopen returns 0 instead of an fd? Should something be said about whether or not mcds are supported one at a time or in groups? I would guess only a "single" channel descriptor is really meaningful? cheers Daryl > > >Number: 80 > >Category: errata > >Synopsis: 17.2.7 omits description of use of fd > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: stefen > >State: open > >Class: errata-simple > >Submitter-Id: etf > >Arrival-Date: Mon Jul 29 02:50:01 PDT 2002 > >Closed-Date: > >Last-Modified: > >Originator: Daryl.Stewart@cl.cam.ac.uk > >Release: 2001b, 17.2.7 > >Organization: > >Environment: > > >Description: > 17.2.7 $ferror does not explain use of "fd" argument. > > $ferror returns error status of last operation on fd. > > Change description to: > > A string description of the error encountered by the most > recent file I/O operation on file descriptor fd is written > into the reg str which should be at least 640 bits wide. > The integral value of the error code is returned in errno. > If the most recent operation on file descriptor fd did not > result in an error, then the value returned shall be zero, > and the reg str shall be cleared. > >How-To-Repeat: > > >Fix: > > >Release-Note: > >Audit-Trail: > >Unformatted: From: Shalom Bresticker <Shalom.Bresticker@motorola.com> To: Daryl Stewart <Daryl.Stewart@cl.cam.ac.uk> Cc: etf-bugs-direct@boyd.com Subject: Re: errata/80: 17.2.7 omits description of use of fd Date: Mon, 29 Jul 2002 14:34:36 +0300 I already thought about both these questions. > Should something be said about using $ferror after $fopen returns 0 instead of > an fd? You will call $ferror with the variable which you used for $fopen. It does not matter whether the value you got back was 0 or a file descriptor number. Either way, $ferror will relate to the correct fd. > Should something be said about whether or not mcds are supported one at a time > or in groups? I would guess only a "single" channel descriptor is really > meaningful? A true mcds is not supported. I thought about several cases where you call $ferror with an invalid fd. It would be the same for any of the functions or tasks which you fd. I guess the response is implementation dependent. Shalom From: Shalom Bresticker <Shalom.Bresticker@motorola.com> To: Daryl Stewart <Daryl.Stewart@cl.cam.ac.uk> Cc: etf-bugs@boyd.com Subject: Re: errata/80: 17.2.7 omits description of use of fd Date: Tue, 30 Jul 2002 16:43:10 +0300 Daryl Stewart wrote: > Should something be said about using $ferror after $fopen returns 0 instead of > an fd? We could. That would be a clarification, not an erratum fix. > Should something be said about whether or not mcds are supported one at a time > or in groups? I would guess only a "single" channel descriptor is really > meaningful? It is like all the other tasks which work on fd's. They don't work on mcds's. Shalom |
Unformatted |
|
Hosted by Boyd Technology