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

Camlp4 bug handling private type definitions #4349

Closed
vicuna opened this issue Jul 20, 2007 · 5 comments
Closed

Camlp4 bug handling private type definitions #4349

vicuna opened this issue Jul 20, 2007 · 5 comments

Comments

@vicuna
Copy link

vicuna commented Jul 20, 2007

Original bug ID: 4349
Reporter: @mmottl
Assigned to: ertai
Status: closed (set by @xavierleroy on 2010-04-29T12:26:16Z)
Resolution: fixed
Priority: normal
Severity: crash
Version: 3.10+dev
Fixed in version: 3.10+dev
Category: -for Camlp4 use https://github.com/ocaml/camlp4/issues
Monitored by: sds @mmottl

Bug description

The following gets into an infinite loop on the terminal and crashes with an assertion failure when writing to file:

camlp4of -str "type t = private [> ]"

@vicuna
Copy link
Author

vicuna commented Jul 25, 2007

Comment author: ertai

It's now fixed in the CVS. Thanks for reporting it.

@vicuna
Copy link
Author

vicuna commented Jul 25, 2007

Comment author: @mmottl

I'm afraid, but the bug has only been partially fixed. Calling camlp4of on a string provided on the command line now works, but putting the type definition in a file and trying to compile it still fails with an assertion failure:

Assertion failed, file "camlp4/Camlp4/Struct/Camlp4Ast2OCamlAst.ml", line 262, char 8
Preprocessor error

It seems only the printer for human-readable output has been fixed, but generating the AST directly still doesn't work.

@vicuna
Copy link
Author

vicuna commented Sep 18, 2007

Comment author: sds

this issue is rather important to us.
is it being worked on?
thanks!

@vicuna
Copy link
Author

vicuna commented Sep 18, 2007

Comment author: @mmottl

Sds, as far as I have been told, this has already been fixed in the CVS.

@vicuna
Copy link
Author

vicuna commented Sep 24, 2007

Comment author: ertai

This now really fixed in the CVS. Thanks for re-reporting it and sorry for the long delay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant