On Jul 25, 2007, at 11:52 AM, [EMAIL PROTECTED] wrote:
Hmmm, so maybe combining a getprogname() call and doing a search of PATH for that value. That would be better than most solutions. It's not a 100% accurate way to determine the executing binary but I can't imagine under what conditions it could go wrong, unless perhaps you had a second version of neko installed.--Dan--
Hi Nicolas,Here's some quick code I threw together with what we talked about (based on latest cvs). I must say that I have never looked at the neko source code before this and even now only looked at vm/main.c so I apologize for the quickly done hack. This does seem to work for me on my FreeBSD box with just a quick call to nekoc, which now returns nothing (as it should heh). I'm not sure about the cross platform compilation of this code however, so it may need to be tweaked if you see something.
Thanks! --Dan--
neko.diff
Description: Binary data
-- Neko : One VM to run them all (http://nekovm.org)
