volks,
I seem to be unclear from such documentation as I have
where exactly does the win32 space begin and end? My
premise had been that this was a 'windowing system' on
the order of M.I.T's Xwindows, Apple's GUI 'classic' and 'Aqua',
and who can forget G.E.M, and ....
and was not 'enmeshed' in the operating system layer - hence
not a requirement for dealing with bios/device drivers etc -
but I keep getting ambiguous references in documentation
"Win32 on NT offers pre-emptive multitasking, separate memory spaces for
individual processes and many other relatively advanced OS features.
Memory handles now point to addresses within each process's private memroy,
with special tricks done by the OS to support situations (DDE &
WM_SETTEXT) where apps assume that they are shared."
http://www.iseran.com/Win32/FAQ/history.html
Assume that I wish to continue to work with linux running on
standard intel based cpu architecture, using consumer grade
mother boards, et al - will I need to extend into dealing with
the win32 API in perl much further than to know that it exists
on non-linux OS machine???
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
