Provide an option to ocamlmktop to continue after top-level exception #6335
Labels
Comments
|
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original bug ID: 6335
Reporter: @johnwhitington
Status: acknowledged (set by @damiendoligez on 2014-07-16T13:31:20Z)
Resolution: open
Priority: normal
Severity: feature
Category: toplevel
Bug description
Let's say I have have run my program to discover a run time error:
$ ./test
Fatal error: exception Invalid_argument("Utility.take")
I build a custom ocaml top-level by default, as many people do. So, I want to play with some of the functions interactively to find my error:
$ ./text.top
Fatal error: exception Invalid_argument("Utility.take")
But I never get to a prompt, so I cannot experiment, without getting the program into a fully functioning state!
I suggest "ocamlmktop -continue" to build a runtime which would produce:
feast:text john$ ./text.top
Fatal error: exception Invalid_argument("Utility.take")
OCaml version 4.01.0
The awkwardness, I suppose, is that if an exception is raised in the initialisation of one module, later modules won't be initialised - is that the problem?
The text was updated successfully, but these errors were encountered: