• 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: access to reparented enclosing script
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: access to reparented enclosing script


  • Subject: Re: access to reparented enclosing script
  • From: has <email@hidden>
  • Date: Wed, 29 Jun 2016 21:08:55 +0100

Mitchell L Model wrote:
Here we go again. Some of my recent experiments were spawned by the following situation, which I badly need to resolve (though for present purposes I have an ugly workaround). I am working on adding ONE DAMN FEATURE to someone else’s sophisticated pair of object-oriented scripts that work just fine.

Sophisticated clusterfuck, I think you mean. Don't even try to be a smartass in AppleScript: it despises it and will royally kick your ass. Aside from not working (did you miss something on line 3?), your code example absolutely reeks of my old ASTest library, which I think I've already said not to use. Perhaps now you can see there's a good reason I burned that horror with fire?

Unfortunately, my new TestTools library is problematic to use too, but that's solely because AppleScript itself is a bugridden pit of Lovecraftian nightmares all the way down; not because there's anything wrong in my design or implementation despite having to resort to the odd bit of code generation to get around AS's other limitations. Alas, something about compiling and appending handlers to to an existing OSAID context causes AppleScript to fart out randomly-generated errors on a completely ad-hoc periodic basis just to screw with your day. Even so if you want a unit test framework you're still infinitely better off using it than that old abominable POS, or anything like it. It still works perfectly 96% of the time and when the AS parser/compiler bug does get tickled you just have to tweak your unit test's source a bit and it magically goes away again.

"Doctor Doctor it hurts when I do this!"

"Well stop doing it then."


has
_______________________________________________
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: windows of app process & spaces
  • Next by Date: Calling an Applet's Library Handlers
  • Previous by thread: access to reparented enclosing script
  • Next by thread: access to reparented enclosing script
  • Index(es):
    • Date
    • Thread