Le 2012-04-25 09:12, Invisible a écrit :
>>> So... how is it ever possible to statically link software?
>>
>> You have to take extra steps to make sure it works.
>
> Really?
>

Yes.  For example: Miocrsoft dictating that all Windows applications and 
DLLs must use the Pascal calling convention.

(I know DLLs are not statically linked... but you get my drift.  If you 
want to use library XYZ, you need to use the same calling convention as 
library X uses.

>> For example, back in
>> the days of Windows 3.1, you had to use the Pascal calling convention
>> for your functions in order to make sure that they could interact with
>> other modules. (Maybe it's still that way, I haven't touched a C program
>> in 15 years.)
>
> So what you're saying is "the C calling convention is undefined, but the
> OS calling convention is not"?

No.  I'm saying - as Darren pointed out - that the C calling convention 
is not undefined, but implementation-defined.  There's a difference.

Division by zero = undefined.
Number of bits in an integer = implementation-defined.

-- 
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/*    flabreque    */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/*        @        */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/*   gmail.com     */}camera{orthographic location<6,1.25,-6>look_at a }

Post a reply to this message