develooper Front page | perl.perl5.porters | Postings from June 2006

Re: Its time we set the score straight on Perl 5 and Perl 6 and debunk our own self-generated FUD.

Thread Previous
From:
Dr.Ruud
Date:
June 20, 2006 07:32
Subject:
Re: Its time we set the score straight on Perl 5 and Perl 6 and debunk our own self-generated FUD.
Message ID:
20060620143208.13496.qmail@lists.develooper.com
"Konovalov, Vadim Vladimirovich (Vadim)** CTR **" schreef:

> IMO CORE should not be bloated by some more Win32 modules.

I don't think it is about that. It is about maximization of core
functionality, on all platforms, in a platform-independent way. And
Win32 is an important platform for Perl.

So maybe Win32::Autoglob should be used by default (if Win32), with a
simple option to not use it.
Alternatively, the perl-installer could create some
'perl -MWin32::PERLIX "%1" %*' registry entry.

Other example: unification of modules like Linux::Mounts and
Win32::DriveInfo. See Sys::Filesystem.



Just some more pointers:

File::HomeDir
Time::Unix

Maybe the documentation of Device::USB should mention
http://libusb-win32.sourceforge.net/

Device::SerialPort almost replaces Win32::SerialPort.
Platfom-independent code should be able to use Device::SerialPort, even
on Win32. http://search.cpan.org/search?query=SerialPort&mode=module
Device::Modem uses either.

Device::ParallelPort has a "plugin" format, to load platform-dependent
drivers. Device::SCSI is also like that.

Is Win32::AbsPath still relevant, or is its functionality already in one
of the main Win32 modules or even in core?

-- 
Affijn, Ruud

"Gewoon is een tijger."



Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About