vm crash when defining method with invalid type name

[Brian Rice]

That's not the VM, it's the condition-handler for methods not found: 
the expression that @ takes is just evaluated, so you get errors there 
just like anywhere else. I /presume/ this relates to the issue I 
mentioned in the other thread about bootstrapping. Try it with the new 
alpha images and let me know if there's still a problem.

On Mar 14, 2005, at 5:38 PM, John Leuner wrote:

> When I use a bogus type to define a method the VM self-destructs ...
>
> jemna% ./vm
> slate.image
> Slate: Growing heap to 6156120 bytes.
> True
> Slate 2> ensureNamespace: #foo.
> (traitsWindow. prototypes. globals. Mixins. Types. VM. foo)
> Slate 3> foo addPrototype: #rock.
> ("rock" traitsWindow: ("rock" traitsWindow: ("Cloneable" ...). traits3:
> ("Cloneable" ...).
>         traits2: ("Cloneable" ...). traits1: ("Cloneable" ...). traits:
> ("rock traits" ...).
>         printName: 'rock'))
> Slate 4> r@(foo rock traits) bar
> [
>  'lard'
> ].
> [bar]
>
> Slate 5> foo rock bar.
> 'lard'
>
> Slate 6> x@(foo rockBOGUS traits) car
> [
> 'slab'
> ].
> Slate: Growing heap to 10350424 bytes.
> Slate: Growing heap to 14544728 bytes.
> Slate: Growing heap to 16777216 bytes.
> Slate: Attempted to grow heap beyond limits
>
>
> I did a checkout (pull) this morning and fetched little.image.
>
> -rw-r--r--  1 jewel jewel 637060 2005-03-12 05:15 little.image
> jemna% md5sum
> little.image
> fd73ae24b69556bf163d33acaccad0a0  little.image
>
>
> John Leuner
>
>
--
Brian T. Rice
LOGOS Research and Development
http://tunes.org/~water/