From: "SooHyoung Oh" <shoh@duonix.com>
To: "Caml-List" <caml-list@inria.fr>
Subject: [Caml-list] [Release] ocaml2: ocaml with editable line history
Date: Thu, 5 Dec 2002 16:01:47 +0900 [thread overview]
Message-ID: <002701c29c2c$2dcf9c70$fe00a8c0@hama> (raw)
I'm very pleased for my first contribution on ocaml world.
<ocaml2> is the ocaml interpreter with editable line history which
implemented using libgetline library.
Please visit http://www.taglib.co.kr/ocaml/index.html and enjoy it.
===================== Readme ==============
What is ocaml2?
If you want to correct mistyped lines in ocaml, ocaml2 is very useful.
It supports editable line histories using libgetline.
See getline manuaual for more information.
Version: ocaml2 version 0.1
Prerequsite: (I tested only on these releases.)
ocaml: version 3.06
libgetline: version 3.9
Files:
README - This file
Makefile - Makefile
getline.ml - external function declarations
log.make - make log
ocaml2.ml - main program
prim_getline.c - C interface functions for libgetline
How to make:
(0) untar and cd in the directory
% tar zxvf ocaml2.tgz
% cd ocaml2
(1) edit Makefile (eg: % vi Makefile)
I assume that "getline.h" is in /usr/local/include and
libgetline.a in /usr/local/lib.
(2) % make
(3) (optional testing) % ./ocaml2
(4) (optional installation)
% su
# make install
How to use:
See getline manual. (eg. % man getline)
---
SooHyoung Oh
http://www.duonix.com
-------------------
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
next reply other threads:[~2002-12-05 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 7:01 SooHyoung Oh [this message]
2002-12-05 10:20 ` Mike Potanin
2002-12-06 1:54 ` Jaeyoun Chung
2002-12-06 7:10 ` Sven Luther
2002-12-06 11:01 ` SooHyoung Oh
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='002701c29c2c$2dcf9c70$fe00a8c0@hama' \
--to=shoh@duonix.com \
--cc=caml-list@inria.fr \
/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).