Giulio Bernardi wrote:
A complicating sideeffect on win64 is that executables(/dlls ?) can be
called from within the WOW32 context.
So multiply your story with WOW/nonWOW and we have more places where
it can go wrong.
AFAIK, it's not possible for a 64 bit binary to load 32 bit code. The
two worlds are isolated (they even see different things for the
same registry key, for example): In fact, on win64 they provide a 64 bit
and a 32 bit Internet Explorer, since 32 bit plugins (like
Flash) cannot be loaded in Internet Explorer - 64 bits.
I know, this is the theory. But does it also count for assemblies ? Does
it also count for internal created cominterfaces ? Does XP handle it
correct internally ?
I cannot tell.
I also read that a 32bit process cannot go outside the WOW. But I do
know that my 32bit debugger can execute a 64bit executable and
manipulate it.... Just to indicate that there are cases of mixed
evnvironments.
I can imagine that an SxS exception would get raised if it happens in
such case.
But as a said earlier, I've to do some reading on this subject.
Marc
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
