caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Zheng Li <li@pps.jussieu.fr>
To: caml-list@inria.fr
Cc: Roberto Di Cosmo <roberto@dicosmo.org>
Subject: Re: [ANN] STMlib and Enhtop available
Date: Tue, 13 Mar 2007 03:08:49 +0100	[thread overview]
Message-ID: <87mz2hlwsu.fsf@pps.jussieu.fr> (raw)
In-Reply-To: <87d53mzbdq.fsf@pps.jussieu.fr>


Hi, list

This is a quick bug-fix and features update to Enhtop since the first
release. Main enhancements include:

  * fixed a serious bug of visiting values from opened modules (Thanks Roberto)
  * new directive #env to set toplevel environment configuration. For now,
    which kinds of declarations get pretty printed is configurable, and we
    make a default configuration different from, and hopefully more rational
    than, the original toplevel setting. 
  * new directive #modu to list all the modules at hand and indicate whether
    they are already loaded or not. 
  * #directory now support the removal of path by prefixing "-"
  * #tell can now distinguish which module the current binding is from, in the
    case that more than one modules have the same identifier and all being
    opened
  * #tell now allow independent access to a single entry of an external
    module. It prints both the value and the type of the visited entry if 
    the module is already loaded, otherwise only the type is printed.
  * *most* of the directives (both original and newly added ones) now get
    "defaults", i.e., when executed without any arguments, they fall back to
    some predefined default functions, which usually provide relevant
    helping information. e.g. #directory will print out current path setting,
    #load will print out the name of all .cmo and .cma currently available etc.
  * the feedback of some directives is improved.

Check changelog and README from its website for more details and examples. 

One thing you should note that, we do not touch source files other than those
inside the "toplevel" directory. I.e. there is no modification to your
compilers (ocamlc/ocamlopt etc.) and libraries, the compilers themselves and
the executables produced by them should remain identical to the originals. So
you're safe and free to switch to it or switch back. We'd like to get more
feedback from more people to improve it.

> This is an experimental patch (we also provide pre-built testing executable and
> Debian package) for an enhanced OCaml toplevel with following features:
>
> For any kind of bindings (i.e. value, type, module, class etc.):
>
>   * Identifiers been rebound are shown differently by default, to distinguish
>     with currently effective ones
>   * A new directive to query (by kinds or names or their composition) and show
>     both current and history bindings
>   * A new directive to show the current binding of any identifier without
>     evaluating or rebinding it
>   * A type-check-only testing mode to experiment your definitions without
>     polluting the world, and the directive to enter/leave it
>
>     http://www.pps.jussieu.fr/~li/software/index.html#enhtop

-- 
Zheng Li
http://www.pps.jussieu.fr/~li


      reply	other threads:[~2007-03-13  2:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 14:37 Zheng Li
2007-03-13  2:08 ` Zheng Li [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mz2hlwsu.fsf@pps.jussieu.fr \
    --to=li@pps.jussieu.fr \
    --cc=caml-list@inria.fr \
    --cc=roberto@dicosmo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).