Re: How to 'load' osaxen
Re: How to 'load' osaxen
- Subject: Re: How to 'load' osaxen
- From: Paul Berkowitz <email@hidden>
- Date: Mon, 18 Jun 2001 07:28:58 -0700
On 6/18/01 6:02 AM, "Stephen Swift (aka Burnum)" <email@hidden> wrote:
>
At 6/17/01 5:24 PM, Paul Berkowitz (email@hidden) Wrote:
>
>
> Now your SA folder is clean of this osax, and you'll see raw codes in any
>
> script that calls it, when compiled. When done with testing, put the saved
>
> copy into the SA folder, call it or "run script" or now your new method of
>
> <<event ascrgdut>> in a try block, to use it again.
>
>
Question: Why do you have to do this in the first place? Why can't you test
>
scripts with the additions in the SA folder? Or is this to ensure that
>
people downloading this script don't need any extra SAs? Thanks
Yes. In the case of something that works for you and not for others, it's to
test whether you're inadvertently taking advantage of an osax (either a
command or a silent coercion) that others don't have: you may have to inform
them that it's required. Or, in the case of something that _doesn't_ work
when you think it should, it can test whether some osax's terms conflict
with application terms or variable names that you're using in your script.
As you surmise, it's obviously important if you're releasing your script to
other users.
--
Paul Berkowitz