Browse thread
ANN OCaml Batteries Included alpha 1
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Peng Zang <peng.zang@g...> |
| Subject: | Re: [Caml-list] ANN OCaml Batteries Included alpha 1 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I think Batteries Included is a great idea and have been looking forward to seeing how it turns out. I've just installed it and have been playing around with it. A quick question, how do you get batteries to work in the toplevel? I tried the usual: # #use "topfind";; # #require "batteries";; No such package: bin_prot.syntax - Required by `batteries.bin_prot.syntax' But I get an error. Attempts to "#require" batteries.bin_prot.syntax yield similar errors. This is quite important to me. I don't know what the general sentiment of the community is, but the toplevel is one of the major reasons I use OCaml. In fact, for every Makefile I write, I write an equivalent toplevel init file. This ensures that any code I write in the toplevel, will compile with no changes and vice versa. Even when making simple edits to compiled code, I will open up a toplevel, load the library/file and open the correct name space of where the edit will take place (automated with some elisp of course). This allows me to test, in the toplevel, each little change I make. Thanks in advance, Peng On Saturday 11 October 2008 09:48:34 am David Teller wrote: > Dear list, > > We're happy to inform you that the first alpha version of OCaml > Batteries Included has just been released. You may find the source on > the Forge [1], as well as the release notes [2], and you can browse the > documentation online, including a detailed presentation of what OCaml > Batteries Included is all about [3]. A GODI package has also been > uploaded for OCaml 3.10 . > > The list of features is a tad too long for detailing it here. Let's just > say that there are new or improved data structures, i/o, unicode ropes, > syntax extensions, primitives for invoking some of the tools of the > toolchain, etc. > > It's alpha-level code, so use with caution, and not all the features we > have in mind have been implemented yet. On the other hand, any form of > feedback is greatly appreciated. > > [1] http://forge.ocamlcore.org/frs/?group_id=17&release_id=44 > [2] http://forge.ocamlcore.org/frs/shownotes.php?release_id=44 > [3] http://forge.ocamlcore.org/docman/?group_id=17 > > Have fun coding, > David -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFI8Y4/fIRcEFL/JewRAst2AKCRnKy/uB70LhSBnb/Rvny2EJTKYwCgz+j+ 1oNcyf/KdXaQrwOe4dChrlk= =zMpC -----END PGP SIGNATURE-----