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
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!
The text was updated successfully, but these errors were encountered:
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.
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!
The text was updated successfully, but these errors were encountered: