From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=HTML_MESSAGE autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id EE38EBBC1 for ; Fri, 25 Apr 2008 18:59:53 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq8IAHaqEUjAXQIm/2dsb2JhbACCNjWkXoUY X-IronPort-AV: E=Sophos;i="4.25,708,1199660400"; d="scan'208";a="10063585" Received: from discorde.inria.fr ([192.93.2.38]) by mail2-smtp-roc.national.inria.fr with ESMTP; 25 Apr 2008 18:59:53 +0200 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id m3PGxrhw015338 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Fri, 25 Apr 2008 18:59:53 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao0BAGarEUhA6aq6d2dsb2JhbACCNjWObgEMBQIECQ+VQYUZ X-IronPort-AV: E=Sophos;i="4.25,708,1199660400"; d="scan'208";a="25499812" Received: from rn-out-0910.google.com ([64.233.170.186]) by mail4-smtp-sop.national.inria.fr with ESMTP; 25 Apr 2008 18:59:52 +0200 Received: by rn-out-0910.google.com with SMTP id i6so1690730rng.2 for ; Fri, 25 Apr 2008 09:59:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=Nm/JuJP94u5uKO/KI+zyUhhRhj38JS9MlYQg7DC/Vpg=; b=l53I/PxLPB2N2eWMNUhprPIyZjtwMbSbdeXJu7+mwVknMYT1j29cRrv2CysF8ULxW6LMkrUI6MsW0RWAPt2CFTRitqPHZxc7LoewqjaWu5LEyTlf6akOuAVG8nTPOipI0QoLA1tAvgCUyP1BExFYBm7KFPZ+ATVYgy9zxGpaq98= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=GuYXCrQ0HvZeW3NZ7kSujlN+ewFDvYkVK/yZxHFijOtbuYOJVUx+9V4yDgQXOE+qPcwuE5RYIqww7kNWQrY75D0aTRtdYgjK9Ho+KVPgorKvNJTwGI2MDj0whJ3mBDlU3WLtzIJ7IWEyOdOUA9qE7lbJIZjLNPOrrMbL97rPJS8= Received: by 10.142.49.4 with SMTP id w4mr968270wfw.185.1209142790715; Fri, 25 Apr 2008 09:59:50 -0700 (PDT) Received: by 10.142.153.9 with HTTP; Fri, 25 Apr 2008 09:59:50 -0700 (PDT) Message-ID: Date: Fri, 25 Apr 2008 18:59:50 +0200 From: "Berke Durak" To: "Richard Jones" Subject: Re: [Caml-list] [OSR] Standard syntax extensions ? Cc: caml-list In-Reply-To: <20080425082447.GB30805@annexia.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_6244_10359130.1209142790717" References: <1209052182.6180.35.camel@Blefuscu> <200804241802.19074.jon@ffconsultancy.com> <20080425082447.GB30805@annexia.org> X-Miltered: at discorde with ID 48120E09.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; berke:01 durak:01 berke:01 durak:01 syntax:01 0200,:01 datatypes:01 datatype:01 syntax:01 compiler:01 cmo:01 cmi:01 cmxa:01 cmi:01 ocaml:01 X-Attachments: cset="UTF-8" cset="UTF-8" ------=_Part_6244_10359130.1209142790717 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Fri, Apr 25, 2008 at 10:24 AM, Richard Jones wrote: > On Thu, Apr 24, 2008 at 10:53:36PM +0200, Berke Durak wrote: > > We absolutely need a standard serialization solution. > > > > I'm thinking of Sexplib of course but it could be another one. The > reason > > it must be standard is that it's difficult to provide > > serialization/deserialization functions outside the imlementation. > > It isn't though. There are several serialization modules (sexplib, > deriving, ...), all of them are packaged up so using them is a simple > 'apt-get' away. But we need at least to enrich standard container datatypes with serialization functions... Do we want to have n copies of each datatype for each serialization library? I think we must agree on one such solution and ensure it is always available. As those solutions all involve syntax extensions, this means that it must go into the list of standard sytnax extensions. > So Sexplib should be a standard extension, or better, it should be > included > > in the compiler and used for the .cmo/.cmi/.cmxa files. > > Why? That would allow people to easily write tools that examine object files without relying on the unnecessarily britlle binary format. At the very least you could open it in a text editor and see if everything's OK inside, or simply grep it. Yes, there is CMI grep, but that one would be even better. Do this, and you will instantly see 10 to 20 new metatools for Ocaml. -- Berke Durak ------=_Part_6244_10359130.1209142790717 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Fri, Apr 25, 2008 at 10:24 AM, Richard Jones <rich@annexia.org> wrote:
On Thu, Apr 24, 2008 at 10:53:36PM +0200, Berke Durak wrote:
> We absolutely need a standard serialization solution.
>
> I'm thinking of Sexplib of course but it could be another one.  The reason
> it must be standard is that it's difficult to provide
> serialization/deserialization functions outside the imlementation.

It isn't though.  There are several serialization modules (sexplib,
deriving, ...), all of them are packaged up so using them is a simple
'apt-get' away.

But we need at least to enrich standard container datatypes with
serialization functions...  Do we want to have n copies of each datatype
for each serialization library? I think we must agree on one such solution
and ensure it is always available.

As those solutions all involve syntax extensions, this means that it must go
into the list of standard sytnax extensions.

> So Sexplib should be a standard extension, or better, it should be included
> in the compiler and used for the .cmo/.cmi/.cmxa files.

Why?

That would allow people to easily write tools that examine object files without
relying on the unnecessarily britlle binary format.  At the very least you
could open it in a text editor and see if everything's OK inside, or simply grep
it.  Yes, there is CMI grep, but that one would be even better.  Do this, and
you will instantly see 10 to 20 new metatools for Ocaml.
--
Berke Durak


------=_Part_6244_10359130.1209142790717--