* Csaba Halász -- Tuesday 23 October 2007:
> In FGNasalListener::call the arguments are set up for the call. [...]
> These end up in naNewGhost, and finally [...]

Umm, but the steady increase of refcounters also happens with simple
Nasal bindings, where listeners aren't anywhere close. There's only
NasalSys::handleCommand() and NasalSys::call() involved, but no
naSave/naRelease/etc. (And in listeners the naSave is there to protect
the callback function *code* from garbage collection, and this is
necessary and can't be given up, as far as I understand. Or the
listener function would just be removed, in which case it can, indeed,
not cause any harm. But won't work, either. But again: this doesn't
seem to be a listener problem, but a more generic one.)

m.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to