From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 80B5D7EE4B for ; Fri, 27 Sep 2013 20:08:32 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of yotambarnoy@gmail.com) identity=pra; client-ip=209.85.128.43; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="yotambarnoy@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of yotambarnoy@gmail.com designates 209.85.128.43 as permitted sender) identity=mailfrom; client-ip=209.85.128.43; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="yotambarnoy@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-qe0-f43.google.com) identity=helo; client-ip=209.85.128.43; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="postmaster@mail-qe0-f43.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlwDAOfIRVLRVYArlGdsb2JhbABbgz9SrXiKEohCgRgIFg4BAQEBBwsLCRIqgiUBAQQBQAEbEgwDAQsGBQQHAxchIQEBEQEFAQoSBgESCAqHYQEDCQYMmziMUoMKhA4KGScDCmSJAAEFDIxagmcLhCADlhaBaYEvixWDShgphGkg X-IPAS-Result: AlwDAOfIRVLRVYArlGdsb2JhbABbgz9SrXiKEohCgRgIFg4BAQEBBwsLCRIqgiUBAQQBQAEbEgwDAQsGBQQHAxchIQEBEQEFAQoSBgESCAqHYQEDCQYMmziMUoMKhA4KGScDCmSJAAEFDIxagmcLhCADlhaBaYEvixWDShgphGkg X-IronPort-AV: E=Sophos;i="4.90,994,1371074400"; d="scan'208";a="34665412" Received: from mail-qe0-f43.google.com ([209.85.128.43]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 27 Sep 2013 20:08:30 +0200 Received: by mail-qe0-f43.google.com with SMTP id gh4so2055283qeb.2 for ; Fri, 27 Sep 2013 11:08:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=61xkWK5HDKfWQIIry28GSp++XbBQuHEXHq2EF+8RNKo=; b=uwvIcsiiVJgWXItEJ9z/dYGdO026URFHQdW2X5XefEw6qeBz0ZsRUp0B3fZDPhvBFM rCeaGYH+4xsbGJ9TbX3C8B1cQoOoJAGqu90lSsVptz2hYx+6rzw2DsIRGH/mmELekinI ByOBxsaowRAiuzC50v5BY8wpbFsFPEOyTVRV7axQmZkCT8TdACPca/prhRLUpwG6jHVp gDl0mLSEJtAXlK6KRN8/iwuyw0WeHrvw4ZYS3fWY9PVwjnSsrB2T+YOqBEjRcmFtrgwq XtxHcVpJPvcPZf+xpit373LT5mP7uFsKv123FwvkuY8RWJ8DCh1czoIBxliG+pt5mGm6 07tQ== X-Received: by 10.229.127.74 with SMTP id f10mr10867339qcs.16.1380305311076; Fri, 27 Sep 2013 11:08:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.139.20 with HTTP; Fri, 27 Sep 2013 11:08:10 -0700 (PDT) In-Reply-To: References: From: Yotam Barnoy Date: Fri, 27 Sep 2013 14:08:10 -0400 Message-ID: To: Dmitry Grebeniuk , Ocaml Mailing List Content-Type: multipart/alternative; boundary=001a1133dd4cbf999a04e7615f71 Subject: Re: [Caml-list] Fwd: Proposal: re-design of ocaml headers --001a1133dd4cbf999a04e7615f71 Content-Type: text/plain; charset=ISO-8859-1 This is a good point. I'm not that familiar with the bindings in ocaml. What I can say is that bindings should be written at an abstract enough level that they don't mess directly with internal bit representations. Using the ctypes library seems like a good way to go. If a bunch of libraries' bindings have to be rewritten because the internal runtime representation has changed... well then maybe that should be done once to allow them to be abstract enough so that future internal changes don't have the same impact. Yotam On Fri, Sep 27, 2013 at 12:20 PM, Dmitry Grebeniuk wrote: > Hello. > > >> (this is a thread about runtime values > >> representation, I suppose.) > > This isn't really relevant to this topic, since this discussion is just > > about ocaml headers, rather than the ocaml C FFI. The FFI would remain > > largely the same. > > There is a lot of bindings have to be rewritten due to these > changes. You can not automate it with C preprocessor. What would you > suggest here? > > -- > 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 > --001a1133dd4cbf999a04e7615f71 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
This is a good point. I'm not that familiar with = the bindings in=20 ocaml. What I can say is that bindings should be written at an abstract=20 enough level that they don't mess directly with internal bit=20 representations. Using the ctypes library seems like a good way to go.=20 If a bunch of libraries' bindings have to be rewritten because the=20 internal runtime representation has changed... well then maybe that=20 should be done once to allow them to be abstract enough so that future=20 internal changes don't have the same impact.

Yotam


On Fri, Sep 27, 2013 = at 12:20 PM, Dmitry Grebeniuk <gdsfh1@gmail.com> wrote:
Hello.

>> (this is a thread about runtime values
>> representation, I suppose.)
> This isn't really relevant to this topic, since this discussion is= just
> about ocaml headers, rather than the ocaml C FFI. The FFI would remain=
> largely the same.

=A0 There is a lot of bindings have to be rewritten due to these
changes. =A0You can not automate it with C preprocessor. =A0What would you<= br> suggest here?

--
Caml-list mailing list. =A0Subscription management and archives:
ht= tps://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

--001a1133dd4cbf999a04e7615f71--