Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002230OCamlOCaml generalpublic2004-02-11 13:032004-02-14 10:33
Reporteradministrator 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0002230: toplevel hiccups on faulty class def
DescriptionFull_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;;

TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0002793)
administrator (administrator)
2004-02-11 21:19

From: henridf@yahoo.com
> 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.

    Jacques Garrigue


- Issue History
Date Modified Username Field Change
2005-11-18 10:14 administrator New Issue


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker