Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grammar bug: expressions are definitions #8301

vicuna opened this Issue Sep 26, 2003 · 2 comments


None yet
1 participant
Copy link

vicuna commented Sep 26, 2003

Original bug ID: 1852
Reporter: administrator
Status: closed (set by @damiendoligez on 2007-12-12T14:54:09Z)
Resolution: fixed
Priority: normal
Severity: minor
Fixed in version: 3.11+dev
Category: documentation

Bug description

The OCAML toplevel accepts

module X = struct 3 + 4 end;;

but the grammar at
says you can only have definitions inside struct...end, and bare
expressions aren't definitions. I think you should add bare
expressions as definitions to the grammar.

Tim Freeman
GPG public key fingerprint ECDF 46F8 3B80 BB9E 575D 7180 76DF FE00 34B1 5C78


This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Jun 16, 2004

Comment author: administrator

It is described in the text but not in the grammar. --DD 2004-06-16


This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Dec 12, 2007

Comment author: @damiendoligez

This will be fixed in 3.11, but be aware that in the grammar
readability primes over faithfulness to the implementation:
the implementation might accept more programs than are
described in the grammar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.