| To: | yyyyyyyyyyyy@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Definition of "can" in XBD |
| From: | Eric Vought <yyyy@xxxxxxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 7 Jul 1999 21:57:43 -0400 (EDT) |
This version reads better and is much less confusing. On Tue, 6 Jul 1999, Shirley Bockstahler-Brandt wrote: > Perhaps some of the confusion arises from the word "optional" in the > definition of "can." In POSIX, we tend to think of an option as being > something the implementation decides about providing. That's not what > is meant in the definition at all. > > Try reading the definition without the adjectives: > Describes a feature or behavior available to the user or application. > The feature or behavior is mandatory for an implementation that > conforms to this document. An application can rely on the existence > of the feature or behavior. > -> Quoting Trimmed <- |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Definition of "can" in XBD, Eric Vought |
|---|---|
| Next by Date: | one-header-per-function, Donn Terry |
| Previous by Thread: | Re: Definition of "can" in XBD, Shirley Bockstahler-Brandt |
| Next by Thread: | one-header-per-function, Donn Terry |
| Indexes: | [Date] [Thread] [All Lists] |