• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: OS X 10.2.x Script Debugger/Applescript bug
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OS X 10.2.x Script Debugger/Applescript bug


  • Subject: Re: OS X 10.2.x Script Debugger/Applescript bug
  • From: Chris Espinosa <email@hidden>
  • Date: Mon, 18 Nov 2002 10:49:31 -0800

On Saturday, November 16, 2002, at 09:50 AM, Paul Berkowitz wrote:

From today's MacFixIt:

Script Debugger bug reveals Mac OS X 10.2.x AppleScript flaw Under Mac OS X
10.2.x, Script Debugger fails to compile large scripts. When attempting to
compile scripts over 3000 lines, the program will return an "out of memory
error." Mark Aldritt of Late Night Software (creators of Script Debugger)
says the bug is actually a reflection on flaws in the AppleScript
implementation, that are simply reported more accurately in Mac OS X 10.2.x:

I'm not sure if that's the same bug, or a different one, that prevents
compilation in Script Debugger mode with medium-size scripts considerably
shorter than the ones that don't compile in regular AppleScript mode. In
fact the description of the "32765 style runs" sounds more like the Debugger
mode bug. Chris Espinosa recently gave a completely different reason for the
long-script AppleScript mode bug, relating to "parts of speech" and some
low-level instruction that was flipped (recently, I think, not
long-standing). And I had specifically tested that bug after removing ALL
formatting styles, and it made no difference.

So someone (MacFixit, probably) has got confused and given the right
explanation for the wrong bug, I think. Awaiting further elucidation and -
eventually - TWO fixes.

No, same bug, different explanation: the "over 3000 lines" is not a hard-and-fast limit as many people have proven; it's just that scripts that long tend to have enough different "parts of speech", each needing its own style run, to trigger the number-of-style-runs bug. And as Mark points out, due to another underlying fix in the OS, this bug is reported as an "out of memory error" in 10.2.

And part of the problem of the bug is that it depends only on the different parts of speech, not different formats for them, so your experiment (setting all formatting the same) doesn't necessarily prove anything. A script of more that 3000 lines, each consisting of the single word "activate", would probably succeed (I've successfully compiled a script of 4,096 such lines).

This bug has been fixed, there's no AppleScript update in 10.2.2 but should be in the next upcoming update.

Chris Espinosa
Apple
_______________________________________________
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.

References: 
 >Re: OS X 10.2.x Script Debugger/Applescript bug (From: Paul Berkowitz <email@hidden>)

  • Prev by Date: Re: AppleScript 1.6 and Mac OS 8.6
  • Next by Date: Error trap if item cannot be made into an integer?
  • Previous by thread: Re: OS X 10.2.x Script Debugger/Applescript bug
  • Next by thread: OS X Finder and file names copy/paste?
  • Index(es):
    • Date
    • Thread