From: drieux
To: [EMAIL PROTECTED]
Sent: 5/10/02 5:08 PM
Subject: Re: win32 specification and API
On Friday, May 10, 2002, at 08:10 , Timothy Johnson wrote:
[..]
>Where the Win32 namespace
such a GEEK - I hadn't even thought of this in terms of
FOO::Win32 and Win32::*
On Friday, May 10, 2002, at 08:10 , Timothy Johnson wrote:
[..]
>Where the Win32 namespace
such a GEEK - I hadn't even thought of this in terms of
FOO::Win32 and Win32::*
as seperable - from the rest of the angst.
I guess my next question in this series - how to
tell - if
On Friday, May 10, 2002, at 08:32 , Jenda Krynicky wrote:
[..]
>>
>> thanks, that had been my working assumption - but it's
>> this problem of sorting out which parts of what goes
>> into a 'windows system' deal with the GUI, the standard
>> construct of a kernel - as would be used in other OS's
From: drieux <[EMAIL PROTECTED]>
> On Friday, May 10, 2002, at 04:45 , Jenda Krynicky wrote:
>
> > No. Win32 means it's meant for 32 bit Microsoft Windows systems :
> > Win95, Win98, WinME, WinNT, Win2k, WinXP, ...
> >
> > While there might be some modules whose name starts with
whatever.
-Original Message-
From: drieux
To: [EMAIL PROTECTED]
Sent: 5/10/02 7:06 AM
Subject: Re: win32 specification and API
On Friday, May 10, 2002, at 04:45 , Jenda Krynicky wrote:
> No. Win32 means it's meant for 32 bit Microsoft Windows systems
> : Win95, Win98, W
"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, lurk
On Friday, May 10, 2002, at 04:45 , Jenda Krynicky wrote:
> No. Win32 means it's meant for 32 bit Microsoft Windows systems
> : Win95, Win98, WinME, WinNT, Win2k, WinXP, ...
>
> While there might be some modules whose name starts with
> Win32 that work on other OSes, it's very unlikely. And not
Subject: win32 specification and API
> 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.
on Fri, 10 May 2002 00:57:29 GMT, [EMAIL PROTECTED] (Drieux) wrote:
> 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 th
