> >>Is there some way of compiling MacPerl scripts into machine language or >>converting them into C/C++ routines that I could then read into >>CodeWarrior... Maybe this would increase speed - then again maybe not?? > >Now why do people always believe that converting Perl code to C will >magically crank up the speed by a factor of 10? 'Cos it won't. I think. It won't, in all cases, but it'll usually do it some. And the resulting binary file will almost always be smaller than a perl text file+the perl interpreter+the libraries. Which can cause things to load much faster, and consume much less memory. This applies to the MacPerl runtime option, too-- I've had MacPerl programs saved in runtime mode end up at 1.5 megs, when the corresponding C code (which would run on its own, without having to load MacPerl to access libraries) would compile to less than 200K. Perl and MacPerl are wonderful, wonderful tools, but they're not suited to *every* application. Though they're oftentimes great for doing mock-ups of even the applications to which, because of speed or size, they're not suited. :) "MTV is the pornography of semiotics."-- Greil Marcus ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch