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

ocaml 3.12.0+dev17, svn revision 10259: revised syntax + new records underscore pattern = syntax error #5024

Closed
vicuna opened this Issue Apr 11, 2010 · 2 comments

Comments

Projects
None yet
1 participant
@vicuna
Copy link
Collaborator

vicuna commented Apr 11, 2010

Original bug ID: 5024
Reporter: Dmitry Grebeniuk
Assigned to: @xclerc
Status: closed (set by @xavierleroy on 2012-09-25T18:06:17Z)
Resolution: fixed
Priority: normal
Severity: minor
Fixed in version: 3.12.1
Category: ~DO NOT USE (was: OCaml general)
Monitored by: @ygrek @hcarty

Bug description

I've downloaded ocaml from svn trunk (revision 10259) and noticed that revised syntax can't handle pattern "_" when matching records:

========================================================
C:\overbld\ocaml>ocaml
Objective Caml version 3.12.0+dev17 (2010-01-20)

#load "dynlink.cma";;

#load "camlp4r.cma";;

    Camlp4 Parsing version 3.12.0+dev17 (2010-01-20)

type myrec = { a : int; b : float };

type myrec = { a : int; b : float }

value f { a = a; _ } = a;

Characters 15-16:
value f { a = a; _ } = a;
^
Error: Parse error: "}" expected after [label_ipatt_list] (in [ipatt])

========================================================

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Apr 12, 2010

Comment author: @alainfrisch

Indeed, none of the new syntactic features in the trunk have been ported to Camlp4 yet.

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Jun 1, 2011

Comment author: @damiendoligez

Still present in 3.12.0 and 3.12.1+dev10

@vicuna vicuna closed this Sep 25, 2012

@vicuna vicuna added the bug label Mar 20, 2019

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.