From: "Nicolás Ojeda Bär" <nicolas.ojeda.bar@lexifi.com>
To: Josh Berdine <josh@berdine.net>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] enabling warnings using compiler-libs
Date: Tue, 30 May 2017 00:18:13 +0200 [thread overview]
Message-ID: <CADK7aFNOg=AObhv88TjYbio5Sv3BhjWcgTQerGGROiKF74axKw@mail.gmail.com> (raw)
In-Reply-To: <jk60ig4lw3tjdg.fsf@fb.com>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Hi Josh,
I think you can use
Warnings.parse_options : bool -> string -> unit
for that. The first flag indicates if the warning should be an error and
the second argument specifies the warnings in the usual format. For
example,
Warnings.parse_options true "+50"
would activate Warning 50 as an error, etc.
Best wishes,
Nicolas
On Mon, May 29, 2017 at 11:59 PM, Josh Berdine <josh@berdine.net> wrote:
> I would like to call e.g. Parse.implementation from compiler-libs with
> warning 50 'Bad_docstring' enabled. Have I overlooked something, or is
> that not possible using the standard exposed interface?
>
> I guess that one warning that involves the parser might not justify the
> overhead of adding an interface?
>
> Cheers, Josh
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 1841 bytes --]
next prev parent reply other threads:[~2017-05-29 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 21:59 Josh Berdine
2017-05-29 22:18 ` Nicolás Ojeda Bär [this message]
2017-05-29 23:17 ` Josh Berdine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADK7aFNOg=AObhv88TjYbio5Sv3BhjWcgTQerGGROiKF74axKw@mail.gmail.com' \
--to=nicolas.ojeda.bar@lexifi.com \
--cc=caml-list@inria.fr \
--cc=josh@berdine.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox