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: 5147 Reporter: Hendrik Tews Assigned to:@xclerc Status: closed (set by @diml on 2016-12-07T17:27:41Z) Resolution: open Priority: normal Severity: feature Version: 3.12.0 Category: -for Camlp4 use https://github.com/ocaml/camlp4/issues
Bug description
This is a feature wish for otags: In the following cases I have
to parse parts of the input a second time (after camlp4) because
there is not sufficient location information available.
Here are the problematic cases:
"type t = ..." : There is no location info for "t" in the
camlp4 ast. This location is non-trivial to compute, because
there might be type parameters between "type" and "t".
"class type x = object val s : int end" : There is no location
info for "s"
same for the "s" in "class type x = object method virtual s : int end"
same for the "s" in "class type x = object method s : int end"
same for the "s" in ``external s : int->int = "xx" '' in
interfaces and structures
same for the "S" in "module S : ..." in interfaces.
same for the "S" in "module type S = ..." in interfaces.
same for the "s" in "val s : int" in interfaces.
same for the "s" in "class t = object val s = 0 end" in
structures.
same for the "s" in "class t = object val virtual s : int
end" in structures.
same for the "s" in "class t = object method virtual s : int
end" in structures.
same for the "s" in "class t = object method s = 0 end" in structure.
same for the "S" in "module S = ..." in structures.
same for the "S" in "module type S = ..." in structures.
The text was updated successfully, but these errors were encountered:
Original bug ID: 5147
Reporter: Hendrik Tews
Assigned to: @xclerc
Status: closed (set by @diml on 2016-12-07T17:27:41Z)
Resolution: open
Priority: normal
Severity: feature
Version: 3.12.0
Category: -for Camlp4 use https://github.com/ocaml/camlp4/issues
Bug description
This is a feature wish for otags: In the following cases I have
to parse parts of the input a second time (after camlp4) because
there is not sufficient location information available.
Here are the problematic cases:
"type t = ..." : There is no location info for "t" in the
camlp4 ast. This location is non-trivial to compute, because
there might be type parameters between "type" and "t".
"class type x = object val s : int end" : There is no location
info for "s"
same for the "s" in "class type x = object method virtual s : int end"
same for the "s" in "class type x = object method s : int end"
same for the "s" in ``external s : int->int = "xx" '' in
interfaces and structures
same for the "S" in "module S : ..." in interfaces.
same for the "S" in "module type S = ..." in interfaces.
same for the "s" in "val s : int" in interfaces.
same for the "s" in "class t = object val s = 0 end" in
structures.
same for the "s" in "class t = object val virtual s : int
end" in structures.
same for the "s" in "class t = object method virtual s : int
end" in structures.
same for the "s" in "class t = object method s = 0 end" in structure.
same for the "S" in "module S = ..." in structures.
same for the "S" in "module type S = ..." in structures.
The text was updated successfully, but these errors were encountered: