On Fri, Feb 09, 2001 at 10:28:49AM -0200, Branden wrote:
> In http://www.w3.org/TR/NOTE-OSD.html#B they describe platform/cpu standard
> names, and we'll definetly need those for checking target architecture. Can
> we standardize upon those, or there's something missing? There's an issue
I take it "Lunix" is Linux.
BSDi isn't FreeBSD, NetBSD or OpenBSD
Nothing they list seems to be VMS
Pace are still developing variants of Acorn's RISC OS to run set top boxes
As I understood it there were about 39 variants of Unix ever, and they seem
to have 12 listed.
Processors are missing
pa risc (nice one, as HP-UX *is* in the OS list)
arm sh ia64 s390
and probably some more
[If I can run 'ls /usr/src/linux/arch/' why can't they? Hmm. Document
dates from 1997. Acorn was trading then]
The ommission of pa risc makes me wonder about quality of the rest of this
document.
> that I really don't know: in the same platform, different compilers generate
> incompatible binaries? Because if this happens (and will still happen on
> Perl 6) the platform identification should be os/cpu/compiler. Perhaps each
on perl 5 different configure options generate different binaries.
> Other important issue I don't know yet: Is there an Archive::Zip module for
> Perl? How cross-platform is it? Can we bundle it with Perl (licensing
http://www.cpan.org/modules/by-module/Archive/Archive-Zip-0.11.readme
> issues)? Is it stable? Will it give us the support we need (access to
> individual files in the archive, and the ability to `fake' them as real
> files through tied filehandles)?
I don't know the answers to the other questions. However, I was intending
to write a layer for perl 5.7 that can access zip entries via regular
perl filehandles. (In theory this could let you run scripts direct out of a
zip without actually unpacking them anywhere)
Layers of some form are needed in perl6 to cope with utf8 and other
encodings, so I would expect the perl6 layer functionality can also be
extended to zip manipulations.
Nicholas Clark
