Francis Leboutte wrote:

> Current version is 1.2 . Too many crashes (application exception ->
> access
> violation), undefined bugs ("hard error") and other various bugs (e.g.
> in
> the inverse functions)...

I removed all uses of inverse fns in our application a long time ago
because the performance was so poor. I was thinking about adding them
now that 1.2 advertises great improvements. Perhaps I should avoid them.

As far as hard errors and access violations, have you checked the
aclxdump.txt files to see if they captured a backtrace?  We have
experienced some access violations (about one every 100 hours of use)
but have not been able to detect a pattern nor get reliable backtraces
in the aclxdump files.  Stack overflows are mostly likely problems in
your code: the aclxdump files should help.

Our current biggest beef with astore 1.2 is that class-prototypes don't
reliably detect unbound class slots, but now that we know that, we are
able to work around it fairly reliably. The "correct solution" is far
more painful in terms of performance than the workaround; so, we opt for
the workaround.

Another problem with 1.2 is that you cannot change the class of an
instance that has the new slot-hashtables. Once again, once you know
that, you can avoid the problem by using the old persistent-hash-tables
in those objects that might change class. No big deal.