auto classes and finalizers

[Mike Capp]

In article <e2378s$gpn$1 at digitaldaemon.com>, Sean Kelly says...
>
>the next release [of Ares] will include a 
>hookable callback in the standard library similar to onAssertError. 
>This will allow the user to decide upon which behavior is most 
>appropriate, and to do so on a per-class basis as I am planning to pass 
>either the original class pointer or simply a ClassInfo object.

To clarify: if the decision is per-class (which I agree it should be), is there
any benefit to catching this error at runtime rather than compile time? Or is it
just that it's easier to try out this way?

cheers
Mike