"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???"
Not really, for the most part.
Starting with the first part, though, the Win32 API is more than just a
GUI implementation on an OS base. It's everywhere, lurking behind every
shadow, laughing at you, analyzing your faults, watching you foolishly
attempt to make a simple program without looking at your copy of the
Platform SDK.
As far as generic Perl programming goes, however, you won't need to use
the APIs, for the most part. Most of your text manipulation, file creation,
directory traversal, etc. is handled by a subsystem that just does it for
you, so it's not like you have to call Win32::FileCreateEx() or something
every time you want to do an open(INFILE,"myfile").
Where the Win32 namespace becomes really useful is on things that are
more or less specific to the OS. Some of the things I use the Win32
namespace for are manipulating the registry, interacting with the scheduler
of a remote machine, software and hardware auditing, setting the time,
setting environment variables(permanent ones), adding users,automating
programs with OLE/COM, determining the nodename(for Win95), and creating
dialogs. These things are very useful in administering a Win32 environment,
but not for making cross-platform programs, because the cross-platform
programs are generally not going to be doing these kind of OS-specific
tasks.
-----Original Message-----
From: drieux
To: [EMAIL PROTECTED]
Sent: 5/9/02 5:57 PM
Subject: win32 specification and API
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]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
