Home My Page Projects Code Snippets Project Openings SML/NJ Bugs
Summary Activity Tracker Lists

[#217] Unhandled exceptions no longer print anything when inside used file

Date:
2018-10-10 20:55
Priority:
3
State:
Closed
Submitted by:
Bug Submitter (webuser)
Assigned to:
John Reppy (jhr)
Machine Architecture:
None
Operating System:
Generic Unix
Component:
Other
Resolution:
Fixed
Severity:
Cosmetic
OS Version:
SML/NJ Version:
110.82 or higher
Keywords:
URL:
Transcript (of reproduction):
Standard ML of New Jersey v110.82 [built: Tue Dec 26 08:16:21 2017] - use "foo.sml"; [opening foo.sml] val test = fn : int -> int val it = () : unit - test; val it = fn : int -> int - test 1; uncaught exception Fail [Fail: foo] raised at: foo.sml:1.35-1.46
Source (for reproduction):
In foo.sml: fun test n = if n = 1 then raise Fail ("foo") else 2; val t = test 1;
Summary:
Unhandled exceptions no longer print anything when inside used file

Detailed description
I don't know if you all would call this a bug or a feature but for
many years an unhandled exception when using a file would print a
failure like:

- use "foo.sml";
[opening foo.sml]
val test = fn : int -> int

uncaught exception Fail [Fail: foo]
raised at: foo.sml:1.35-1.47

But in 110.82 or higher, we are met with no indication an
exception was raised.
Additional comments:
Compared to 110.81:

- use "foo.sml";
[opening foo.sml]
val test = fn : int -> int

uncaught exception Fail [Fail: foo]
raised at: foo.sml:1.35-1.47




Submitted via web form by Dan Grossman <djg@cs.washington.edu>

Comments:

Message  ↓
Date: 2019-04-23 12:35
Sender: John Reppy

Fixed in 110.86 (see #219 also)

Date: 2018-10-10 21:43
Sender: John Reppy

This is a duplicate of bug #193.

Attached Files:

Changes

Field Old Value Date By
status_idOpen2019-04-23 12:35jhr
close_dateNone2019-04-23 12:35jhr
summaryunhandled exceptions no longer print anything when inside used file2019-04-23 12:35jhr
ResolutionAccepted As Bug2019-04-23 12:35jhr
summaryunhandled exceptions no longer print anything2019-04-23 12:34jhr
assigned_tonone2018-10-10 21:43jhr
detailsI don't know if you all would call this a bug or a feature but for many years an unhandled exception when using a file would print a failure like: - use "foo.sml"; [opening foo.sml] val test = fn : int -> int uncaught exception Fail [Fail: foo] raised at: foo.sml:1.35-1.47 But in 110.82 or higher, we are met with no indication an exception was raised. Additional comments: Compared to 110.81: - use "foo.sml"; [opening foo.sml] val test = fn : int -> int uncaught exception Fail [Fail: foo] raised at: foo.sml:1.35-1.47 Submitted via web form by Dan Grossman <djg@cs.washington.edu> 2018-10-10 21:43jhr
ResolutionNone2018-10-10 21:43jhr
Transcript (of reproduction)Standard ML of New Jersey v110.82 [built: Tue Dec 26 08:16:21 2017] - use "foo.sml"; [opening foo.sml] val test = fn : int -> int val it = () : unit - test; val it = fn : int -> int - test 1; uncaught exception Fail [Fail: foo] raised at: foo.sml:1.35-1.46 2018-10-10 21:43jhr
Source (for reproduction) In foo.sml: fun test n = if n = 1 then raise Fail ("foo") else 2; val t = test 1; 2018-10-10 21:43jhr