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

RFE: an ocamllex flag to keep it a bit more quiet #8254

Closed
vicuna opened this issue Aug 28, 2003 · 1 comment
Closed

RFE: an ocamllex flag to keep it a bit more quiet #8254

vicuna opened this issue Aug 28, 2003 · 1 comment

Comments

@vicuna
Copy link

vicuna commented Aug 28, 2003

Original bug ID: 1803
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)

Bug description

Full_Name: Aleksey Nogin
Version: 3.06
OS: RedHat Linux 8.0
Submission from: mojave1.cs.caltech.edu (131.215.44.186)

Currently ocamllex prints out messages like "85 states, 1501 transitions, table
size 6514 bytes" (this comes from Output.output_lexdef) which are somewhat
distracting when ocamllex is called as a part of a compilation of a large
project (where I would expect the output to be produced only when something is
wrong). It would be nice if ocamllex supported something like a --quiet option
that would inhibit such diagnostic output (but still allow warnings). Thanks!

@vicuna
Copy link
Author

vicuna commented Aug 29, 2003

Comment author: administrator

Currently ocamllex prints out messages like "85 states, 1501 transitions,
table
size 6514 bytes" (this comes from Output.output_lexdef) which are somewhat
distracting when ocamllex is called as a part of a compilation of a large
project (where I would expect the output to be produced only when something
is
wrong). It would be nice if ocamllex supported something like a --quiet
option
that would inhibit such diagnostic output (but still allow warnings). Thanks!

This is now implemented in the working source (option -q).
Thanks for the suggestion.

-- Damien

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