From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by yquem.inria.fr (Postfix) with ESMTP id 48812BBAF for ; Sat, 23 Jan 2010 00:13:27 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq0BANe/WUvRVd+/kGdsb2JhbACSDIljPwEBAQEJCQwHEwOtLYFAhSKIBwEBAwWENwSDIQ X-IronPort-AV: E=Sophos;i="4.49,327,1262559600"; d="scan'208";a="42319013" Received: from mail-iw0-f191.google.com ([209.85.223.191]) by mail3-smtp-sop.national.inria.fr with ESMTP; 23 Jan 2010 00:13:26 +0100 Received: by iwn29 with SMTP id 29so1366731iwn.1 for ; Fri, 22 Jan 2010 15:13:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=SiQ9CD/9X9F5z/0mmQVf/MIezxv0cPAQ5PwcKjlvXak=; b=GCAcnkkpankTp7MdWFCpvEPsRVmRbk7XBMIkN3K4zJEeKrug2d+TkECjgP90gZzNzr 5iKLthh6HMehaHhT499HSnZeC9n3djNbWi3tBDRKL/piL4u+B00siEAs6AoXe3c4q/uw AOYja6/KnOwtl0OFSRp7/w6th9/osY7ioKR4w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=An2KCT8sSqAdO7bf5kivAZaHnII8brZdvaUrc5QeZ9elqNSg+FPqp2zNMOqiDni3NV HwCnSul4ud1+xdE55YGHk6Zy9feavuFnZpQE8kRdq2tiZwCp3Eaxwmwytdi2gq24CrJI m843NPUPfoIol7UAX9o2m7SYINwZlRmTpKEm8= Received: by 10.231.168.133 with SMTP id u5mr5886002iby.29.1264202005364; Fri, 22 Jan 2010 15:13:25 -0800 (PST) Received: from ?192.168.1.98? ([72.44.99.175]) by mx.google.com with ESMTPS id 22sm2079203iwn.0.2010.01.22.15.13.23 (version=SSLv3 cipher=RC4-MD5); Fri, 22 Jan 2010 15:13:23 -0800 (PST) Message-ID: <4B5A3112.4020100@gmail.com> Date: Fri, 22 Jan 2010 18:13:22 -0500 From: Edgar Friendly User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre MIME-Version: 1.0 To: Tiphaine Turpin Cc: caml-list@yquem.inria.fr Subject: Re: [Caml-list] Batteries Included 1.0.0 References: <4B51DC6B.6010903@gmail.com> <4B596486.90103@irisa.fr> In-Reply-To: <4B596486.90103@irisa.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam: no; 0.00; dependencies:01 ocaml:01 syntax:01 ocaml:01 intentional:01 intentional:01 enum:01 bug:01 -thread:01 ocamlfind:01 makefile:01 bug:01 howto:01 wiki:01 edgar:98 On 01/22/2010 03:40 AM, Tiphaine Turpin wrote: > Thank you for your work on batteries. Here are a few comments that I > have, having "migrated" my source code to this new version. > I appreciate your taking the time to give feedback. > First, I appreciate the reduction of dependencies. This makes it much > more reasonable to share code using batteries. > > Thank you. > On the negative side, my greatest concern is about outdated > documentation : I found it very difficult to know what had changed, and > how to adapt my code. These changes range from the deletion of some > features I'm glad you were able to wade through the new codebase and adapt. > (batteries/ocaml* tools, myocamlbuild.ml, "open in" syntax > extension, implicit "open Batteries") to minor API changes I'm not convinced that the batteries/ocaml* tools were useful - can people weigh in on this? Ocamlbuild should have a global directory for packages to install their own tag extensions, allowing most users to omit myocamlbuild.ml files from their directory. "Open in" should be replaced soon in ocaml proper, implicit "open batteries" seems a bad idea IMHO. > (naming of > Standard, Data, Shell modules, Intentional - flattened structure > no more Different_list_size exception, Intentional - too many exceptions. > no more Queue.enum...). Should be fixed now, a point release should come out within the week. > Also, there seems to be a packaging bug which > requires using -thread in the ocamlfind command. > Needs fixing. Added to issues tracker. > So, I spent a significant time replacing my old 1-line ocamlbuild > command by a real Makefile (also because of a strange and probably > unrelated linking bug which I still don't fully understand). I believe > that an updated compiling howto is really needed, as well as a list of > the main deleted features with respect to the last release, allowing > users to estimate how much change their code will need. > I still use ocamlbuild with the old myocamlbuild.ml to compile my projects. <*>: pkg_batteries, thread is the main line in my _tags file I need. Would it help to use a wiki to keep track of these things? All my code is already adapted to the new system, so I don't find regressions anymore to record. > Other than that, I have not found any regression or other problems in > this new release of the library, and I'm looking forward to see its > further development. > > Tiphaine > I'm happy to push this forward, and there's a lot of good to add. Patches welcome. E.