Re: Donkey Strikes Again !
- From: "f0dder" <f0dder_nospam@xxxxxxxxxxxxxxxx>
- Date: Fri, 29 Jul 2005 04:57:05 +0200
randyhyde@xxxxxxxxxxxxx wrote:
> This is *all* preserve means. You seem to think that "preserve" is an
> *active* verb, requiring the emission of machine instructions to
> explicitly save a register value and explicitly restore that value
> later on. Preserve does not require this. All preserve means is that
> when you leave a procedure, the (affected) registers have the same
> values they had upon entry. You may *passively* preserve a register
> by simply NOT CHANGING ITS VALUE during the procedure's execution. As
> best I can tell, this is exactly what f0dder is saying.
>
It's what I've been trying to say, anyway. I was seriously starting to
doubt whether my english skills were less than sub standard. Given that
you, donkey and a number of other people get what I mean, I guess I can
have a sound nights sleep now.
I'll stick to my "callbacks are where you MUST preserve", by the way;
if you exit a callback routine with one of the 'critical' registers
being modified, you should expect at least one windows version or service
pack to crash. And as noted in previous posts, sticking with the standard
ABI is a good idea even in places where you don't need to (ie., your own
internal routines).
.
- Follow-Ups:
- Re: Donkey Strikes Again !
- From: hutch--
- Re: Donkey Strikes Again !
- From: randyhyde
- Re: Donkey Strikes Again !
- References:
- Re: Donkey Strikes Again !
- From: randyhyde
- Re: Donkey Strikes Again !
- Prev by Date: Re: C'Mon, this *isn't* Rocket Science
- Next by Date: Re: C'Mon, this *isn't* Rocket Science
- Previous by thread: Re: Donkey Strikes Again !
- Next by thread: Re: Donkey Strikes Again !
- Index(es):
Relevant Pages
|