From: Carlos Eduardo Lenz <lenz@inf.ufsc.br>
To: Christian Lindig <lindig@eecs.harvard.edu>
Cc: Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] ANNOUNCE: Tools from the C-- Project
Date: Tue, 5 Mar 2002 09:51:40 -0300 (EST) [thread overview]
Message-ID: <Pine.GSO.4.10.10203050940520.10919-100000@venus> (raw)
In-Reply-To: <20020304205545.GC10992@lakeland.eecs.harvard.edu>
Does anyone on the list uses Plan9?
It is possible to port Ocaml to Plan9?
I think it whould consist of:
-translating the configure script to an mkfile.
-converting ocamlyacc.
-converting Ansi C to Plan 9 C in byterun/.
-converting the assembler files.
I don't have the knowleage, nor the time, but I can test.
ps: Ocaml whould make Plan 9 much more productive, even without Tk or Gtk.
Thanks,
Carlos E Lenz
lenz@inf.ufsc.br
On Mon, 4 Mar 2002, Christian Lindig wrote:
>
> The C-- compiler project releases internal development tools.
>
> http://www.cminusminus.org/tools.html
>
> OCamlError 1.0
>
> When an Objective Caml byte code program dies with an uncaught exception
> or assertion failure, it can hint at the origin of the exception with a
> stack trace. A stack trace lists module names and source code positions
> in modules as character offsets from the beginning of the corresponding
> source file. Because editors support navigation best by line and column
> numbers, tracking down the origin of an assertion is somewhat tedious.
> OCamlError reads a stack trace and annotates it with readable and
> editor-friendly source code positions. When source code preprocessors
> introduce CPP-style #line directives, these are also honored.
>
> OCamlError is implemented as a literate program with the Noweb tool
> (http://www.eecs.harvard.edu/~nr/noweb) and comes with everything to
> compile it from source code. The documentation is in HTML and Unix
> manual page format. OCamlError is released into the public domain.
>
>
> OCamlBurg 1.0
>
> OCamlBurg is a code generator generator: it takes a pattern matching
> specification and generates a dynamic-programming algorithm that
> implements the matching. Unlike an ML pattern, a Burg pattern covers
> only part of a tree. Dynamic programming finds at run time the cheapest
> way to cover a tree with patterns. The typical application is inside a
> compiler to translate an expression tree into code that evaluates the
> expression at run time. OCamlBurg is inspired by Fraser, Hanson, and
> Proebsting's IBurg implementation for C
> (http://www.cs.princeton.edu/software/iburg).
>
> Like OCamlError, OCamlBurg is implemented as a literate program and
> comes with everything to build it from the source. It is released into
> the public domain as well.
>
>
> Mk from Plan 9
>
> Mk is a successor to Make designed by Andrew Hume. It is used at Bell
> Labs and in Plan 9. While conceptually close to Make, it has resisted
> feature bloat and shines at the details. In particular, variable
> handling in Mk is unified with the sh(1) shell which is typically used
> to execute actions. The result are simple and understandable mkfiles,
> the equivalent to Makefiles.
>
> Mk is distributed as C source code that was extracted from the Plan 9
> source release and ported to Unix. It comes with documentation in PDF
> format and a manual page. Mk is released under the Nuova Open Source
> License.
>
>
> Christian Lindig <lindig@eecs.harvard.edu>
> Norman Ramsey <nr@eecs.harvard.edu>
> -------------------
> To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
> Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2002-03-05 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 20:55 Christian Lindig
2002-03-05 12:51 ` Carlos Eduardo Lenz [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=Pine.GSO.4.10.10203050940520.10919-100000@venus \
--to=lenz@inf.ufsc.br \
--cc=caml-list@inria.fr \
--cc=lindig@eecs.harvard.edu \
/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