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
At present we don't show line numbers when a program crashes at run-time. However we persist line numbers in debug builds so it should be possible, in theory, to extract these from the stack trace and display in the error message.
The text was updated successfully, but these errors were encountered:
--debug cannot be used with --run. The latter creates an in-memory dynamic module and debuggable is not a feature of dynamic modules. Instead we need to change the semantics of --run so it always saves and then it runs the generated executable directly from disk. Consequently we can drop support for dynamic modules in Fortran.
The Comal interpreter, however, still requires dynamic modules. However because debugging cannot be added, any run-time exceptions will not have line numbers. One way around this would be for the interpreter to always generate a persistent assembly and run that instead. Interactive statements could be handled by appending to an internal array of lines and executing those lines in sequence.
At present we don't show line numbers when a program crashes at run-time. However we persist line numbers in debug builds so it should be possible, in theory, to extract these from the stack trace and display in the error message.
The text was updated successfully, but these errors were encountered: