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
Based on recent improvements such as "ocamlrun -b" should Printexc.catch be
deprecated? If i use Printexc.catch then my exception is "caught" and so the
ocamlrun -b will not give a backtrace. If i do not use Printexc.catch it seems
that the message is always as good as the message emitted by Printexc.catch
(regardless of whether i used ocamlc or ocamlopt to create the executable).
This lends me to believe that Printexc.catch serves no useful purpose and in
fact can only be a detriment.Is there something I am missing? Maybe all that is
required is some additional information to the Printexc module document.
The text was updated successfully, but these errors were encountered:
This lends me to believe that Printexc.catch serves no useful purpose and in
fact can only be a detriment.Is there something I am missing?
I agree with your analysis: Printexc.catch no longer serves any useful
purpose, and prevents ocamlrun -b and ocamldebug from handling the
stray exception correctly. The docs should mark this function as
"deprecated, do not use".
Original bug ID: 369
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: John Gerard Malecki
Version: 3.01
OS: any/all
Submission from: 192.149.105.76 (192.149.105.76)
Based on recent improvements such as "ocamlrun -b" should Printexc.catch be
deprecated? If i use Printexc.catch then my exception is "caught" and so the
ocamlrun -b will not give a backtrace. If i do not use Printexc.catch it seems
that the message is always as good as the message emitted by Printexc.catch
(regardless of whether i used ocamlc or ocamlopt to create the executable).
This lends me to believe that Printexc.catch serves no useful purpose and in
fact can only be a detriment.Is there something I am missing? Maybe all that is
required is some additional information to the Printexc module document.
The text was updated successfully, but these errors were encountered: