Date: Sun, 31 Oct 1999 23:05:42 -0800 From: "David O'Brien" <obrien@freebsd.org> To: Randell Jesup <rjesup@wgate.com> Cc: freebsd-arch@freebsd.org Subject: Re: stpcpy() Message-ID: <19991031230542.B10904@dragon.nuxi.com> In-Reply-To: <ybuu2n7gg1x.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net>; from rjesup@wgate.com on Mon, Nov 01, 1999 at 01:24:10AM %2B0000 References: <199910312349.CAA02684@tejblum.pp.ru> <ybuu2n7gg1x.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> I'll bet 95% of programmers working on systems where stpcpy has been > part of the libraries for a long time don't even know that it isn't > standard. I don't doubt that. Other than BDE and myself, I don't even know of anyone that even has the ANSI-C standard. > I don't know about you, but I code for systems where cutting CPU usage > by 1% can actually make a real difference in the field and to costs. > Perhaps this won't get me 1% - but a fraction of a percent here and > another there adds up, and this is at truely zero cost. So you don't program in C, you use ASM. So you don't program in C++, you use C. Going "down" a step in each of these cases will save you much more than 1%. > While non-ANSI standard, this particular function has been > virtually standard in PC compilers for a Long Time. Like I said, near the > start of this, probably for more than a decade it's been in every > DOS/Win/Amiga/OS2/etc compiler I've used (unless my memory fails me, which > it might). It isn't in Micro$oft C version 6. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991031230542.B10904>