Compiler Specific Operators
purtill at petrus.UUCP
purtill at petrus.UUCP
Thu Jul 17 01:44:02 AEST 1986
In article <505 at cubsvax.UUCP> cubsvax!peters (Peter S. Shenkin) writes:
> In article <umcp-cs.2424> chris at maryland.UUCP (Chris Torek) writes:
> >Apparently the committee (or a large faction thereof) is quite
> >concerned about ensuring that there is some easy way to ensure a
> >`real function call'.
> Yes, apparently so, but WHY? What the hell difference does it make, from
> the user's point of view? That is, why should he ever be anything other
> than happy, if some alternative invoked by the compiler produces faster-
> running code?
>
> Peter S. Shenkin Columbia Univ. Biology Dept., NY, NY 10027
> {philabs,rna}!cubsvax!peters cubsvax!peters at columbia.ARPA
Ever heard of debugging? You might well want to set a trap at that
function, or even replace it with a different version that is somehow
useful, such as a version that prints out its arguments.
mark purtill (201) 829-5127
^.-.^ Arpa: purtill at bellcore.com 435 south st 2H-307
((")) Uucp: ihnp4!bellcore!purtill morristown nj 07960
More information about the Comp.lang.c
mailing list