Article View: comp.lang.eiffel
Article #1185Re: Beware of "C" Hackers -- A rebuttal to Bertrand Meyer
From: Larry Weiss
Date: Sat, 23 Mar 1996 20:13
Date: Sat, 23 Mar 1996 20:13
26 lines
1940 bytes
1940 bytes
Peter Seebach wrote: > > >In the old days, when the Standard library was just another set of linkable > >entry points, it was straightforward to replace the vendor's logic with > >your own (maybe just the same with tracepoint logic, but maybe a very > >experimental replacement, and maybe a "better" one). No more! > > It's still straightforward; you write your own logic, and then use a function > which uses your logic. If your logic doesn't work, you just make the function > a stub around the library routine. > > This is SOP if you don't quite like the semantics of a library call, and also > makes it easier to work around vendor bugs. > > I don't do it for most calls, but I bring it in occasionally. > > For instance, most of the functions in the stdlib that take a single > char * argument, I have stubs for which take (char *, ...) and do > "the right thing" with vsprintf. Easy! > I don't understand. Suppose that I want to substitute my strlen() logic for the vendors implementation of strlen() in such a way that not only my source's calls on strlen() are affected, but also any 3rd party's library's uses of strlen() get the "benefit". How does your technique apply to that scenario?
Technical Details
Message-ID:
<31545B86.4CC0@iadfw.net>Path:
arc1-ca.pugleaf.net!news.iadfw.net!usenetReferences:
<1995Jul3.034108.4193@rcmcon.com> <4i862r$1evq@saba.info.ucla.edu> <64ss5$3F3RB@herold.franken.de> <314DADD4.3DE@oc.com> <4j1gmu$crl@solutions.solon.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!news.iadfw.net!usenet From: Larry Weiss <lfw@iadfw.net> Newsgroups: comp.lang.eiffel,comp.lang.c,comp.lang.c++,comp.object,comp.software-eng Subject: Re: Beware of "C" Hackers -- A rebuttal to Bertrand Meyer Date: Sat, 23 Mar 1996 14:13:58 -0600 Organization: customer of Internet America Message-ID: <31545B86.4CC0@iadfw.net> References: <1995Jul3.034108.4193@rcmcon.com> <4i862r$1evq@saba.info.ucla.edu> <64ss5$3F3RB@herold.franken.de> <314DADD4.3DE@oc.com> <4j1gmu$crl@solutions.solon.com> NNTP-Posting-Host: dal20-22.ppp.iadfw.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.01 (Win16; I)