> Kenn Humborg said:
>> > o So how the fsck is the mail message data ending up in the
> > Excel process? Does OLE32.dll use some undocumented memory
> > allocation kernel API that doesn't clear memory? Eek!
>> if I recall correctly, DLLs on Windows have their own memory allocation
> pools. So if OLE32.dll deals with a DLL call from (let's say) Outlook,
> followed by one from Excel, could conceivably wind up with bits of mail
> in the middle of an Excel block of data.
>> I think ;)
Nope. That's only for 16-bit DLLs. 16-bit apps under
Windows are a complete mess. You really don't want to
know about the fscked up memory management issues that
you have to deal with.
32-bit apps are normal, regular, real-operating-system
processes where DLLs get loaded into each process
individually. (Of course unmodified code pages get mapped
as shared memory, just like in Linux.)
If you read any Windows developer magazines and books
around the time of the big Win32 push (NT3.5/Win95), you'll
remember how they made a big deal of this. The upshot was
that in order to share memory between two processes, you
used memory mapped files. Just like any real OS :-)
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!