Message-Id: <5.0.2.1.0.20001217024611.025a3680@pop5.banet.net>
X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Sun, 17 Dec 2000 02:50:51 -0500
To: djgpp-workers AT delorie DOT com
From: "Peter J. Farley III" <pjfarley AT banet DOT net>
Subject: Re: Locking fcntl changes #2
In-Reply-To: <200012162106.QAA18996@envy.delorie.com>
References: <5 DOT 0 DOT 2 DOT 1 DOT 0 DOT 20001216154442 DOT 025a6620 AT pop5 DOT banet DOT net>
 <5 DOT 0 DOT 2 DOT 1 DOT 0 DOT 20001215204828 DOT 032b0030 AT pop5 DOT banet DOT net>
 <5 DOT 0 DOT 2 DOT 1 DOT 0 DOT 20001213204815 DOT 025a7ec0 AT pop5 DOT banet DOT net>
 <5 DOT 0 DOT 2 DOT 1 DOT 0 DOT 20001215204828 DOT 032b0030 AT pop5 DOT banet DOT net>
 <5 DOT 0 DOT 2 DOT 1 DOT 0 DOT 20001216154442 DOT 025a6620 AT pop5 DOT banet DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

At 04:06 PM 12/16/00 -0500, DJ Delorie wrote:
 >> OK, no problem.  Internally, filelength is actually __filelength 
now,
 >> with a "#define filelength __filelength" in 
"/include/libc/stubs.h".
 >> I can put the #define into stubs.h for __lfilelength, and comment 
it
 >> out if there is no such animal elsewhere.
 >
 >The *only* time you put something in stubs.h is if an ANSI/POSIX
 >function in libc needs to call a non-ANSI/POSIX function in libc, in
 >which case the non-ANSI/POSIX function needs to be listed in stubs.h.
 >(or, for ansi functions calling posix-only functions).
 >
 >There is no other reason why a function would get listed in stubs.
 >
 >The "stubbed" name (__foo) is *not* part of the published API.

Well, in this case we already had a POSIX function, fcntl, calling a 
non-ANSI function, filelength, which is why I would then presume that 
the #define for filelength was *already* in stubs.h.  Since fcntl will 
now be calling lfilelength, doesn't the same rationale apply for the 
location of a define for lfilelength?

---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org OR
                      pjfarley AT banet DOT net)