And semantically, I think of it not as the executable's path--that just happens to be something that's 1:1 with a particular copy of parrot. And definitely not libparrot's path--embedded cases would have to specify the path explicitly, though they could partially mimic the same scheme.
I take that back--the path to the library might actually work just as well (and may or may not be less ambiguous to find; the dynamic linker had to find it, and may have left breadcrumbs). This is all, by the way, exactly the NSBundle/CFBundle API from Mac OS X (and before that, OpenStep). See: <http://developer.apple.com/documentation/Cocoa/Reference/Foundation/ ObjC_classic/Classes/NSBundle.html>.
JEff
