Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!burl!codas!killer!richardh
From: richardh@killer.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C vs. Library function names
Message-ID: <1652@killer.UUCP>
Date: Sat, 26-Sep-87 19:00:14 EDT
Article-I.D.: killer.1652
Posted: Sat Sep 26 19:00:14 1987
Date-Received: Sun, 27-Sep-87 22:19:18 EDT
References: <9130@ut-sally.UUCP>
Organization: The Unix(R) Connection, Dallas, Texas
Lines: 17
Keywords: How do you pre-empt them?
Summary: Turbo C peek() is also a macro

In article <9130@ut-sally.UUCP>, nather@ut-sally.UUCP (Ed Nather) writes:
> The only real problem I've encountered is when I have named a function
> of mine with the same name Turbo uses as a library function ... e.g. peek().
> In MSC, library functions are selectively ignored if you have already defined
> a function using the same name in your code, but Turbo gets all upset about 
> it, and refuses to acknowledge my inalienable right to pick overlapping names 
> for my functions.  That's a simple way to replace a library funtion you
> don't like.
> 

If you look in DOS.H, you'll discover that peek() is first declared as a
function and then #defined as a macro. Could there be a conflict between
the use of your own peek() function and this macro definition ?

richard hargrove
...!ihnp4!killer!richardh
-------------------------