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: 373 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: feature Category: ~DO NOT USE (was: OCaml general)
Bug description
If you write a program which prints out information to stdout,
and you get an uncaught exception, the pending contents of
stdout will not be shown.
This makes it easy for a programmer to misinterpret where the
error occurred.
A workaround is to fill the program with 'flush stdout', however
it would be much easier if the top-loop called 'flush stdout', and
maybe other open files before exiting and showing
'Fatal error: uncaught exception...'
/mattias
The text was updated successfully, but these errors were encountered:
If you write a program which prints out information to stdout,
and you get an uncaught exception, the pending contents of
stdout will not be shown.
This makes it easy for a programmer to misinterpret where the
error occurred.
This is a very good point. It should be possible to flush at least
stdout and stderr before printing the message. Thanks for the
suggestion.
Original bug ID: 373
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)
Bug description
If you write a program which prints out information to stdout,
and you get an uncaught exception, the pending contents of
stdout will not be shown.
This makes it easy for a programmer to misinterpret where the
error occurred.
A workaround is to fill the program with 'flush stdout', however
it would be much easier if the top-loop called 'flush stdout', and
maybe other open files before exiting and showing
'Fatal error: uncaught exception...'
/mattias
The text was updated successfully, but these errors were encountered: