Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!linus!alliant!merk!spdcc!ima!dirtydog!karl
From: karl@ima.isc.com (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: Parameter mismatch legality question
Message-ID: <1990Nov19.163927.16624@dirtydog.ima.isc.com>
Date: 19 Nov 90 16:39:27 GMT
References: <1990Nov15.224353.155@mozart.amd.com> <14486@smoke.brl.mil> <14502@smoke.brl.mil> <571@mtndew.Tustin.CA.US>
Sender: news@dirtydog.ima.isc.com (NEWS ADMIN)
Reply-To: karl@ima.isc.com (Karl Heuer)
Organization: Interactive Systems
Lines: 17

In article <571@mtndew.Tustin.CA.US> friedl@mtndew.Tustin.CA.US (Stephen Friedl) writes:
>In article <14502@smoke.brl.mil>, gwyn@smoke.brl.mil (Doug Gwyn) writes:
>>... you're best off if you let <fcntl.h> declare open() for you.
>
>Unless of course you are IBM building the RS6000, where the prototype
>in <fcntl.h> omits the /const/ type qualifier on the pathname.  Mighty
>nice of them not to burden us with qualifiers, eh?

In this case it's still true that the correct action is use <fcntl.h>
rather than declaring it yourself; but you should also reject the broken
implementation and replace it with a working one.

In the situation you describe, the simplest way to get a working
implementation is to edit the vendor's <fcntl.h> to fix the bug, or if this
isn't feasible, to maintain your own copy of the include directory.

Karl W. Z. Heuer (karl@ima.isc.com or uunet!ima!karl), The Walking Lint