-
Notifications
You must be signed in to change notification settings - Fork 11
Use raises wrong exception #60
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't workingcompilerproblem with compilerproblem with compilergforgebug (or feature request) ported from smlnj-gforge repositorybug (or feature request) ported from smlnj-gforge repositoryinvalidThis doesn't seem rightThis doesn't seem right
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingcompilerproblem with compilerproblem with compilergforgebug (or feature request) ported from smlnj-gforge repositorybug (or feature request) ported from smlnj-gforge repositoryinvalidThis doesn't seem rightThis doesn't seem right
Version
110.96
Operating System
OS Version
vista
Processor
x86 (32-bit)
Component
Core system
Severity
Minor
Description of the problem
When exported code (i.e., by exportML or exportFn) calls "use" and the
used code raises an exception, the exception we get isn't the one that
was raised, but ExnDuringExecution instead.
This happens in any code exported by exportFn, and it happens in code
exported by exportML if "use" is called before the REPL goes back to
console for input.
Additional comments:
There's a workaround: always use
exportMLand use a script to sendconsole input to start the program. But that's really clunky.
Transcript
Expected Behavior
No response
Steps to Reproduce
Additional Information
No response
Email address
crary@cs.cmu.edu
Comments from smlnj-gforge
Original smlnj-gforge bug number 303
Submitted via web form by Karl Crary crary@cs.cmu.edu on 2022-03-28 at 14:53:00
comment by @dmacqueen on 2022-04-12 18:28:00 +000 UTC
This is not a bug but a "misuse" of the "use" function, which is only intended to work in the top-level REPL.