On Thu, 2005-03-03 at 18:45 -0500, Tom Metro wrote: > In any case, portable bytecode is helpful, but I think we'll still see a > certain percentage of modules that need to be compiled.
Bytecode IS compiled. Don't confuse terms, here. I think you're saying that some of them would need to talk to C libraries. That's handled, as you speculated it might, in most cases without compiling anything. Parrot has the ability to call out to dynamically loaded code without compilation. See http://cpan.uwinnipeg.ca/htdocs/ponie/pdd16_native_call.html > Unless someone > deems it worthwhile to rewrite, say the MySQL network protocol > libraries, in Parrot. Almost certainly. I imagine quite a lot of code will be re-written in Parrot, if for no other reason than the fact that it allows it to port to any Parrot platform without changes, and that's not always the case with the C library in question (e.g. this would give VMS a stable MySQL interface). _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
