Re: XCode Applescript debugger not stopping at break points
Re: XCode Applescript debugger not stopping at break points
- Subject: Re: XCode Applescript debugger not stopping at break points
- From: email@hidden
- Date: Fri, 11 Nov 2005 07:26:31 -0500
I tried Smile in the past, but I found its behavior and error messages
to be not very consistent. Then again, XCode 1.5 crashes regularly when
debugging multiple files, so maybe it is time to take a second look at
Smile. Thanks for the reminder.
You wrote in your previous email:
I don't know if I'll respond to your problem.
I have C code that I develop with Xcode and I run the code from
Applescript under Smile
(<http://www.satimage.fr/software/en/index.html>) using AppleEvents to
communicate between Smile and the C-code.
I use Xcode-Debugger to debug the Xcode.
Under Smile, each Applescript line or selction of line can be run
sequentially. So it is really easy to see where the Apllescript code
breaks.
Thus I can debug each line I write (C or Applescript).
Regards,
Bernard
Le 10 nov. 05, à 01:11, Thomas Engelmeier a écrit :
Cooperation between AppleScript and gdb has never been very reliable.
It's a
lot better in more recent versions of XCode. My advice in your case is
to
forget it. Just use a lot of "log" statements and "display dialog"
calls. m.
Not that it's terribly important, but gdb is not used to debug
AppleScript in Xcode. Both Java and AppleScript have separate
debugging mechanisms from those used for the C-based family of
languages.
Doesn't change the fact that you have problems with the AppleScript
debugger (though it does mean I don't have to fix it :-)
I hope at least some IS fixing them.
Sorry to say, refactoring an AppleScript Studio app with XCode the last
bunch of days is partially responsible for an extreme lack of sleep on
my side and contributed quite a lot to a really bad IDE experience.
- XCode is the first AppleScript editor that won't point to the
location of compile errors.
- XCode messes up the AppleScript sources beyond osacompile
compilability when they are defined as UTF-8. After a bunch of saves
there is garbage after <option>- <returns>
- When the project has more than one script, the debugger is not only
close to useless. (Where is Scripter? Why can't we use Scripter with AS
Studio?)
Regards,
Tom_E
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
Bernard
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden