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: 2230 Reporter: administrator Status: closed Resolution: not a bug Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
if i enter the following (faulty) class definition in the toplevel, it gets
"stuck" (meaning that i have to C-c C-c to get the prompt again) rather than
rejecting it outright.
class a = object method one = s#1 end;;
The text was updated successfully, but these errors were encountered:
if i enter the following (faulty) class definition in the toplevel, it gets
"stuck" (meaning that i have to C-c C-c to get the prompt again) rather than
rejecting it outright.
class a = object method one = s#1 end;;
This actually the expected behaviour of the lexer: a # followed by an
integer is interpreted as a line number, to provide correct error
messages with preprocessors.
So, this is not a bug.
But I agree that this behaviour is confusing at toplevel.
Original bug ID: 2230
Reporter: administrator
Status: closed
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: henri dubois-ferriere
Version: 3.07+2
OS: debian
Submission from: lcavpc14.epfl.ch (128.178.8.51)
if i enter the following (faulty) class definition in the toplevel, it gets
"stuck" (meaning that i have to C-c C-c to get the prompt again) rather than
rejecting it outright.
class a = object method one = s#1 end;;
The text was updated successfully, but these errors were encountered: