delorie.com/archives/browse.cgi | search |
Date: | Mon, 04 Nov 2002 21:52:31 +0300 |
From: | "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il> |
Sender: | halo1 AT zahav DOT net DOT il |
To: | djgpp-workers AT delorie DOT com |
Message-Id: | <9003-Mon04Nov2002215230+0200-eliz@is.elta.co.il> |
X-Mailer: | emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 |
In-reply-to: | <Pine.A41.4.05.10211041726220.24300-100000@ieva06> (message from |
Andris Pavenis on Mon, 4 Nov 2002 17:30:59 +0200 (WET)) | |
Subject: | Re: LIBC 2.04 new function atoll() implementation |
References: | <Pine DOT A41 DOT 4 DOT 05 DOT 10211041726220 DOT 24300-100000 AT ieva06> |
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 |
> Date: Mon, 4 Nov 2002 17:30:59 +0200 (WET) > From: Andris Pavenis <pavenis AT lanet DOT lv> > > Somebody may want to have member of some structure > or class with this name. I once run into trouble as had a member function > named printf in class which does similar thing as printf does, but > send output somewhere else related to that class. You shouldn't be doing this: the standard says that the names of all the standard functions are reserved, so no other identifier can use them.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |