You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 6301 Reporter:@Chris00 Status: acknowledged (set by @damiendoligez on 2014-07-16T11:44:33Z) Resolution: open Priority: normal Severity: minor Platform: x86_64 OS: GNU/Linux OS Version: 3.10.25 Version: 4.01.0 Category: standard library Monitored by:@dbuenzli
Bug description
The documentation of Printexc.catch says it is deprecated because "the runtime system is now able to print uncaught exceptions as precisely as [Printexc.catch] does". However, that is not entirely true (even) when exception pp are registered. On my machine, the attached code prints:
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.
Original bug ID: 6301
Reporter: @Chris00
Status: acknowledged (set by @damiendoligez on 2014-07-16T11:44:33Z)
Resolution: open
Priority: normal
Severity: minor
Platform: x86_64
OS: GNU/Linux
OS Version: 3.10.25
Version: 4.01.0
Category: standard library
Monitored by: @dbuenzli
Bug description
The documentation of Printexc.catch says it is deprecated because "the runtime system is now able to print uncaught exceptions as precisely as [Printexc.catch] does". However, that is not entirely true (even) when exception pp are registered. On my machine, the attached code prints:
Uncaught exception: Err.E(A)
Fatal error: exception Err.E(0)
File attachments
The text was updated successfully, but these errors were encountered: