raising a non-condition objects raises weird condition

[GoogleCodeExporter]

What steps will reproduce the problem?
(raise 1)

What is the expected output? What do you see instead?
On top-level:
Exception:
    error in raise: unhandled exception has occurred
#<compound-condition #<record &assertion > #<record &who "record-rtd" > 
#<record 
&message "record required, but got 1" > #<record &irritants () > >

In REPL:
 Condition components:
   1. &assertion
   2. &who: "record-rtd"
   3. &message: "record required, but got 1"
   4. &irritants: ()

These conditions are raised by the implementation, not by the user. I did raise 
1, and it was not 
handled anywhere, so the 1 should be handled by the top-level exception 
handler, nonetheless, 
&assertion condition was raised for violating argument assertion of record-rtd.

What version of the product are you using? On what operating system?
mosh rev. 991 on MacOSX 10.4.11

Original issue reported on code.google.com by dico.leq...@gmail.com on 29 Jan 2009 at 8:34

[GoogleCodeExporter]

Original comment by hige...@gmail.com on 30 Jan 2009 at 5:35

• Changed state: Accepted

[GoogleCodeExporter]

Thanks. Fixed on trunk revision 1101.

(1) REPL
  mosh>(raise 1)

  Unhandled exception:

    Non-condition object:
       1

(2) script file
% ./mosh work.scm

 Non-condition object:
     1

 Exception:
     error in raise: returned from non-continuable exception

 Stack trace:
    1. throw: <subr>
    2. (raise c):  compiler-with-library.scm:3078
    3. eval: <subr>
    4. (dynamic-wind in body out):  compiler-with-library.scm:2997
    5. (dynamic-wind in body out):  compiler-with-library.scm:2997
    6. (dynamic-wind in body out):  compiler-with-library.scm:2997
    7. (<top-level>): <unknown location>

Original comment by hige...@gmail.com on 30 Jan 2009 at 7:45

• Changed state: Fixed