On Thu, Sep 28, 2006 at 09:36:13AM +0100, Nicholas Clark wrote: > > However, step 2 is easier for Perl because we're not trying to do portable > bytecode. Some constants, (such as *most* of the socket constants, but I think > not all) are defined in RFCs, so can be baked into bytecode at compile time. > But other constants (such as POSIX limits) are per system, so a complete > solution needs a way of knowing how to defer baking those constants until > load time. Or maybe it doesn't call them "constant" as far as bytecode > interpretation goes, but any JIT or AOT can see that they are, and treat them > accordingly.
Mentioning sockets got me thinking about APR... Has anyone seriously looked at using it for doing portable I/O? -J --
pgpT9ZjngBpWb.pgp
Description: PGP signature
