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.4 required=5.0 tests=AWL,DNS_FROM_RFC_ABUSE autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by yquem.inria.fr (Postfix) with ESMTP id 5C0E5BC6B for ; Wed, 19 Sep 2007 23:54:49 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ah4FABs38UbZDAs+bGdsb2JhbACOEgsEBgcHEgc X-IronPort-AV: E=Sophos;i="4.20,275,1186351200"; d="scan'208";a="1061685" Received: from smtp008.mail.ukl.yahoo.com ([217.12.11.62]) by mail1-smtp-roc.national.inria.fr with SMTP; 19 Sep 2007 23:56:04 +0200 Received: (qmail 2264 invoked from network); 19 Sep 2007 21:56:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr; h=Received:X-YMail-OSG:In-Reply-To:References:Mime-Version:Content-Type:Message-Id:Cc:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer; b=fQsrmBGBpKlG9TYswEYnHQjuwBkpr2o/QXNsNrpJ6NzDLISitho5GUyBilDKsHku0e4UhbDtCl0ZbLhIj7I9YyGcmAlKfHRXdJEWzXvU6y3IPIvNu0rF2LAa5p1yQQDOHIEFxxR+lOhfeyY7FBFJPKu9DmR9qVuYcwzW1Zr/QWg= ; Received: from unknown (HELO ?192.168.0.11?) (vincent.aravantinos@82.229.199.66 with plain) by smtp008.mail.ukl.yahoo.com with SMTP; 19 Sep 2007 21:56:03 -0000 X-YMail-OSG: fwrJqfEVM1mADChX6diLMuZHiPJexT0vbfjLFI2RJqC1.QfTBITy0IxCR6bOPe07qxZYIjeEp1sf5PKTzWpDbOI- In-Reply-To: <20070919214938.76e4fa8b@localhost.localdomain> References: <20070917163617.0e6e0e7c@localhost.localdomain> <20070918085310.GB12115@localhost> <20070918161246.1ff37e29@localhost.localdomain> <200709181742.27747.jon@ffconsultancy.com> <20070919214938.76e4fa8b@localhost.localdomain> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <2BA4BA28-3981-4570-9719-10285B87E802@yahoo.fr> Cc: caml-list@yquem.inria.fr Content-Transfer-Encoding: quoted-printable From: Vincent Aravantinos Subject: Re: [Caml-list] Having '<<', why to use '|>' ? Date: Wed, 19 Sep 2007 23:56:01 +0200 To: Fabrice Marchant X-Mailer: Apple Mail (2.752.2) X-Spam: no; 0.00; experimented:01 ocaml:01 camlp:01 cheers:01 sourceforge:01 wrote:01 rec:01 rec:01 caml-list:01 append:02 consistent:02 lsl:03 ops:03 let:03 tue:06 Le 19 sept. 07 =E0 21:49, Fabrice Marchant a =E9crit : > On Tue, 18 Sep 2007 17:42:27 +0100 > Jon Harrop wrote: > >>> A 3 chars operator (<<<) doesn't look smart. >> That is actually the F# for lsl. There are also ||| and &&& for =20 >> bitwise ops. > > Thanks Jon, happy to read you, > > So, do you think that (<<<) could replace (<<) as a function =20 > composition operator ? > >>> However, about (@@), I preferred to see the direction of the =20 >>> asymmetric >>> composition operator. ( <| ) instead of ( << ) ? Is this a =20 >>> possible idea ? > >> But "<<" is the converse of ">>" (in F#) and "|>" has no converse =20 >> (or you >> could say that "x |> f" is the converse of "f x"). > > Things must keep consistent, you're right. So, ( <| ) instead of =20 > ( << ) > can't be used. > Julien proposed ( @@ ). > > However I saw it was used this way : > > let rec ( @@ ) l1 l2 =3D List.rev_append l1 l2;; ( Why rec ? ) > > here : > http://sourceforge.net/project/showfiles.php?group_id=3D178291 > > It would be useful that experimented OCaml people suggest a =20 > replacement for the heavily used composition operator ( << ) that =20 > is now reserved for camlp4... And how about (<<-) or (<--) ? Cheers, Vincent=