more on cdecl (no flames)

Peter J Desnoyers peter at athena.mit.edu
Sun Apr 24 16:16:13 AEST 1988


I just saw something interesting in the man pages for some Harris
computer I use (I'm embarrassed I don't know the model number) 
that is relevant to the (civilized part of the) cdecl discussion 
that was going on earlier:

If log, exp, etc. are declared as "fortran float log();" instead of
"double log();" then the compiler will generate the inline 
instructions flog, fexp,... (or whatever the names were)

It seems, like cdecl, to be a reasonable way to solve a non-portable
problem. I think the reason why cdecl angered so many people is
because it is a solution (not a bad one) to a botch brought on by
failure to standardize calling conventions, aggrevated by the design
of the processor.

				Peter Desnoyers
				peter at athena.mit.edu
				



More information about the Comp.lang.c mailing list