Re: Possible bug.
Re: Possible bug.
- Subject: Re: Possible bug.
- From: Axel Luttgens <email@hidden>
- Date: Mon, 03 May 2004 15:00:16 +0200
Paul Berkowitz wrote:
On 5/2/04 8:43 PM, "deivy petrescu" <email@hidden> wrote:
Paul, sorry, but I have to take it back!
You are right. It is a problem with periodic fractions.
But looking at it again, it seems like bug.
And using your own words "inconsistent implicit coercion."
Inconsistent behavior is consisten with a bug!
If it handles complicated operations it should also handle divisions.
Long or short results. Or, not handle any at all.
That's not really the point. AppleScript can do the arithmetic.
' run script: Run a specified script or script file
run script script -- the script text (or an alias or file reference of
a script file) to run
it doesn't say anything about 'number' or 'real', does it? 'run script' can
run a text script or a script file. So give it text, like it's asking for.
IMHO, should coerce the number into a string.
If you give it a number, all bets are off. you can't call it a bug when it
fails to do what's undocumented in the first place. It so happens that some
silent coercion works when you give it a rational number but not an
irrational one. So what? You shouldn't be giving it a number in the first
place. It's awfully simple to make an explicit coercion 'as string' - every
time - so you never need to know that you could omit that for certain types
of numbers.
Perhaps, but...
run script ((1 / (2 ^ 3 + 1)) as string)
--> Un(e) , ne peut pas se trouver aprhs ce numiro.
:-)
Axel
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.