I wrote

> Hi,
> 
> Ruby's current (admittedly pointless) ability to instantiate
> ``higher order'' meta classes bunches a hole in the new
> defenses around the allocate frame work. The following script
> segfaults on ruby 1.7.3 (2002-08-29) [i386-mswin32]. (Also see
> [ruby-talk: 38612]).  Maybe this is a good enough reason to
> to identify Class and Object.meta(1)?

Never mind .. I run this script with in RDE and picked
a wrong (older) interpreter - the new improved allocate
catches this mistake ...

/Christoph