If possible, it would also be nice if you'd copy the report into OpenRadar, so that anyone can read it.

So, you should file a documentation bug. ☺


#import "Appscript/Appscript.h"

int main (int argc, const char * argv[]) {
NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];

// Create AEMApplication object for building AEMEvents
AEMApplication *app = [[AEMApplication alloc] init];

// Create AEMCodecs object for unpacking script results
AEMCodecs *codecs = [[AEMCodecs alloc] init];

// Create 'aevtoapp' (run) AEMEvent
AEMEvent *evt = [app eventWithEventClass:kCoreEventClass
eventID:kAEOpenApplication];

// Build direct parameter for 'run' event and add it to AEMEvent
NSMutableArray *params = [NSMutableArray array];
int i;
for (i=1; i < argc; i++)
[params addObject: [NSString stringWithUTF8String: argv[i]]];
[evt setParameter:params forKeyword:keyDirectObject];

// Compile (or load) the AppleScript
NSAppleScript *scpt = [[NSAppleScript alloc] initWithSource:
@"on run params\n"
@" return params as text\n"
@"end run"];

// Get an NSAppleEventDescriptor from AEMEvent
NSAppleEventDescriptor *evtDesc = [evt descriptor];

// Send event to AppleScript
NSDictionary *error = nil;
NSAppleEventDescriptor *resultDesc = [scpt executeAppleEvent:evtDesc
error:&error];

if (resultDesc) {
// Unpack script result
id res = [codecs unpack:resultDesc];
NSLog(@"Result = %@", res);
} else
NSLog(@"Script error = %@", error);

[scpt release];
[codecs release];
[app release];
[pool release];
return 0;
}

Uses objc-appscript's AEM API for building events and converting ObjC values to NSAppleEventDescriptors and back. Plus NSAppleScript (which does indeed leak like a sieve on 10.4 and earlier, although I believe it's somewhat improved in 10.5) for executing scripts, but you could replace that with OSAScript easily enough if you wanted.

HTH

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

1. to handler-name is a valid way to start a handler. It's synonymous with on handler-name.
2. run is a reserved word: reserved for the name of the main handler (synonymous with just putting all your code at the top level, if you don't have any other handlers). That's what I wanted.
3. You only need parentheses after the handler name if the handler is not run. For the run handler, the parentheses are optional.
4. OSA, OSA Kit, and my program all accept text-only (.applescript) scripts, and treat them equally to how they treat compiled (.scpt) scripts. (How to prove this: Compile the script, then run my program on the result. You'll see the same result.)

I sincerely thank you for trying, but none of the advice you gave applies.


on my_run()
beep
end my_run


I have now fixed it. Thanks for the report.

It definitely does not work with the run handler. Calling OSAGetHandlerNames shows the run handler as an Apple Event descriptor rather than a string descriptor, so that may be the problem there.

But I couldn't get it to work with a specific handler, either—I got the same result either way. (Yes, I did add a message to call that handler specifically.)