Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Tiphaine Turpin <tiphaine.turpin@inria.fr>
To: caml-list@inria.fr
Cc: Thomas Gazagnaire <thomas.gazagnaire@gmail.com>,
	Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
Subject: [Caml-list] [ANN] TypeRex release 1.0.0 candidate 2
Date: Fri, 02 Mar 2012 14:47:40 +0100	[thread overview]
Message-ID: <4F50CF7C.4040904@inria.fr> (raw)

Hi everyone,

This is time for a second release candidate for TypeRex, our new
OCaml development environment for Emacs. We want to thank the many early 
adopters, for their useful feedback and encouraging comments.

The new version is available on TypeRex website at:

http://www.typerex.org/

It fixes a number of issues, here is the list of changes:

- Improved performance on large libraries (lazy environments, more cache)
- Fixed encoding bug with 3bytes utf8 characters
- Use line/column positions instead of absolute bytes (fixes windows eol)
- More robust ml/mli switching (contributed by Wojciech Meyer)
- Fixed camlp4 first-class modules
- Compiles with 3.11.2 as claimed (no more 3.12 syntax in the code)
- Made the prefix key customizable (C-o by default)
- Added option --disable-version-check to configure script
- Source extensions customizable (e.g., .eliom), mlp included by default
- Allow to disable syntax coloring completely
- Applied Jun Furuse's indentation patch and changed a few defaults
- Use the caml-mode error regexp instead of tuareg's
- Fixed coloring of constructors in type definitions
- Fixed the crash when starting emacs on several files (>=3)
- Fixed wrapper for -a
- Less risky names in lisp code
- Slightly improved documentation (ocamlbuild, libraries, module packing)
- Tuareg actions use TypeRex stdlib path instead of hard-coded default


Summary of TypeRex features:

     * Improved syntax coloring
     * Auto-completion of identifiers (experimental)
     * Browsing of identifiers: show type and comment, go to definition,
       cycle between alternate definitions, and semantic grep;
     * Strictly semantic-preserving, local and whole-program refactoring:
           o renaming identifiers and compilation units
           o open elimination and reference simplification
     * Robust /w.r.t./ not-recompiled, possibly unsaved buffers
     * Scalable (used regularly on a few hundreds of source files)


Tiphaine Turpin
Thomas Gazagnaire
Fabrice Le Fessant




                 reply	other threads:[~2012-03-02 13:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F50CF7C.4040904@inria.fr \
    --to=tiphaine.turpin@inria.fr \
    --cc=Fabrice.Le_fessant@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=thomas.gazagnaire@gmail.com \
    /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