David Cantrell wrote:
brian d foy wrote:
<[EMAIL PROTECTED]> wrote:
Hopefully it will be something like:
$I::don't::bother::to::write::portable::code=1;
;-)
Seriously though, I would expect things in Win32::* to only work on
Windows, things in Linux::* only to work on linux, and so on for many
other sections (including Mac::* where I have some modules). Portable
code isn't always the goal.
I want my code to be more like File::Spec, which provides a common
interface to a load of platform-specific modules. That has very good
coverage of bizarro OSes, and I think we'd all agree that it's an
excellent example of a nice portable module.
It doesn't work on RISC OS though.
I suppose that this is less that RISC OS is so truly bizzare that it
defies anyone to come up with platform-specific File::Spec code for it,
and more a gentle nudge on your part for someone to find the tuits to do so?
David
--
"It's overkill of course, but you can never have too much overkill."
