[armedbear-devel] Why field LispStatckFrame.UNAVAILABLE_ARG is not static ?

Mark Evenson evenson at panix.com
Sat Aug 10 08:28:43 UTC 2013

On 8/10/13 7:11 AM, Dmitry Nadezhin wrote:
> Memory profiling of ABCL shows that the classes with largest allocation count are
> LispStackFrame and LispStackFrame.UnavailableArgument .
> It seems to me that LispStatckFrame.UNAVAILABLE_ARG can be a singleton object, can't it ?

Indeed the "unavailable argument" abstraction should be a singleton.

Committed in [14572][] (with an unfortunate, inadvertent, superfluous 
change of Netbeans build artifacts).

[14572]: http://lisp.not.org/trac/armedbear/changeset/14572

Thanks for the profiling!

"A screaming comes across the sky.  It has happened before, but there
is nothing to compare to it now."

More information about the armedbear-devel mailing list