Re: [MacPerl] Problem w/making runtime version of script

[schinder@pobox.com]

On Mon, Aug 09, 1999 at 11:20:53PM -0700, Bruce Van Allen wrote:
} 
} On the other hand, besides being ignorant of a relatively new module, 
} I think  what I said was correct -- Perl couldn't find a module. And 
} what I said about true/false is what I've learned from the wizards of 
} this list -- don't bother with variables for TRUE or FALSE.  Finally, 
} what _is_ the answer to the poster's question, if not a missing 
} module? Perhaps a better reply would have been to ask the poster to 
} check their Perl installation...

Yes, you don't need to bother with TRUE and FALSE in Perl, but the
usage was not *wrong*, and it wasn't not-Perl, either.  You don't have
to bother with TRUE and FALSE in C, either, but people do it all the
time, as a visual aid.  People with experience with languages that
have actual Boolean types find it simpler to define such things in
languages that don't have Booleans, just so they don't have to
remember how TRUE and FALSE are defined.

The answer to the question (which if I remember right was about a
standalone runtime; I'm not about to hit the archives for this) is
probably that constant.pm didn't get inserted into the resource fork
of the runtime.  All modules that a runtime that's intended to be used
on a machine that doesn't have MacPerl installed have to be in the
resource fork in the right way, so that MacPerl can find and use them.
There are tools to help with this, but I don't remember if they're
flawless.  Since I never use runtimes, I don't have any experience
with them.


} 
} Thanks again.
} 
} 1;
} 
} 
} 
} 
} - Bruce
} 
} __Bruce_Van_Allen___bva@cruzio.com__831_429_1688_V__
} __PO_Box_839__Santa_Cruz_CA__95061__831_426_2474_W__
} 

-- 
Paul Schinder
schinder@pobox.com

===== Want to unsubscribe from this list?
===== Send mail with body "unsubscribe" to macperl-request@macperl.org