• 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: debugging [was Re: Script Objects]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: debugging [was Re: Script Objects]


  • Subject: Re: debugging [was Re: Script Objects]
  • From: has <email@hidden>
  • Date: Wed, 20 Jan 2010 23:31:01 +0000

Wayne Melrose wrote:

> On 19. jan. 2010, at 19.25, Stockly, Ed wrote:
>
>> I don't like Script Objects because they're a pain to debug.
>
> Same..

You should both file Radar requests asking that AppleScript includes a stack trace [1] in every error report. It's an elementary debugging feature found in most any language, and it's crazy that AppleScript doesn't have it. The more folks that ask for this feature, the more motivation Apple has to address those requests.

Regards,

has

[1] For those not familiar with the term, a stack trace tells you every handler that was called and the line it was called from up to the point at which the error occurred. Very useful.

--
Control AppleScriptable applications from Python, Ruby and ObjC:
http://appscript.sourceforge.net

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users

This email sent to email@hidden

  • Prev by Date: Re: Inconsistency
  • Next by Date: Re: 0 for 2
  • Previous by thread: Re: 0 for 2
  • Next by thread: Finder scripting
  • Index(es):
    • Date
    • Thread