caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: ygrek <ygrek@autistici.org>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] When to (not) use -no-naked-pointers?
Date: Sat, 4 Jul 2015 19:40:27 -0700	[thread overview]
Message-ID: <20150704194027.1e7cd196@kiwi.local.tld> (raw)
In-Reply-To: <20150526102146.721d236c@kiwi.local.tld>

On Tue, 26 May 2015 10:21:46 -0700
ygrek <ygrek@autistici.org> wrote:

>  I wonder if there is a C define in caml runtime headers to test for this configuration feature?
>  Because naturally the bindings author knows whether his code is compatible with this mode or not
>  and could assert that during the build.. 

Answering my own question, NO_NAKED_POINTERS will be defined in config.h if this feature is enabled.

-- 

      reply	other threads:[~2015-07-05  2:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25  6:25 Jez
2015-05-25 21:49 ` Fabrice Le Fessant
2015-05-26 15:42   ` Mark Shinwell
2015-05-26 17:21     ` ygrek
2015-07-05  2:40       ` ygrek [this message]

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=20150704194027.1e7cd196@kiwi.local.tld \
    --to=ygrek@autistici.org \
    --cc=caml-list@inria.fr \
    /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;
as well as URLs for NNTP newsgroup(s).