At 02:30 PM 8/8/2003, Todd Niec wrote:
How does code warrior handle stack usage for unamed temporary variables?
I have a procedure that creates lots of unnamed temporary variables as a
result of conversion operators. I can see that, in terms of
constructors
and destructors, these temporaries are
How does code warrior handle stack usage for unamed temporary variables?
I have a procedure that creates lots of unnamed temporary variables as a
result of conversion operators. I can see that, in terms of
constructors
and destructors, these temporaries are being created and destroyed as
#pragma stack_cleanup on
will cause the compiler to remove items from the stack as soon as a
function returns.
AHA. the temporaries in question are all being passed to a function...
Are there dissadvantages to using that pragma? speed might be one. Is
the speed difference signficant?
speed
How does code warrior handle stack usage for unamed temporary variables?
I have a procedure that creates lots of unnamed temporary variables as a
result of conversion operators. I can see that, in terms of
constructors
and destructors, these temporaries are being created and destroyed as
the
