Go to file
Alain Frisch a2acbc8d3b Adding extension/attribute on patterns.
git-svn-id: http://caml.inria.fr/svn/ocaml/branches/extension_points@13335 f963ae5c-01c2-4b8c-9fe0-0dff7051ff02
2013-03-04 13:52:23 +00:00
asmcomp [coloring] Validate physical register offsets. 2013-01-13 16:57:36 +00:00
asmrun Revert bad commit. 2013-01-23 08:41:02 +00:00
boot Revert bad commit. 2013-01-23 08:41:02 +00:00
build PR#5461: fix warnings 31 in camlp4 compilation 2013-02-18 12:09:06 +00:00
bytecomp #5546: change compilation scheme for nested structures (improve compilation time and sometimes runtime performance as well). Patch by F. Le Fessant. 2012-12-13 15:40:25 +00:00
byterun fix a few of the warnings given by newer versions of gcc 2013-02-26 12:47:13 +00:00
camlp4 Continue. 2013-03-04 12:54:57 +00:00
compilerlibs Install compiler internals (as libraries + compiled interfaces + start modules) 2012-05-17 16:04:13 +00:00
config config/Makefile.*: remove DBM-related variables. 2012-12-30 03:12:09 +00:00
debugger PR#5116: abide english typography in debugger messages. 2012-10-17 12:26:42 +00:00
driver Merge short-paths into a fresh branch of trunk. 2013-01-29 14:21:12 +00:00
emacs merge patch by Stefan Monnier from PR#5884 2013-01-17 02:56:00 +00:00
experimental pprintast 2013-02-01 02:21:21 +00:00
lex remove all $Id keywords 2012-10-15 17:50:56 +00:00
man PR#5928: Missing space between words in manual page for ocamlmktop 2013-02-26 10:36:33 +00:00
ocamlbuild [ocamlbuild] Real time update of the tests, by flushing the channel after each test result. 2013-01-23 23:57:14 +00:00
ocamldoc Continue. 2013-03-04 12:54:57 +00:00
otherlibs Adding extension/attribute on patterns. 2013-03-04 13:52:23 +00:00
parsing Adding extension/attribute on patterns. 2013-03-04 13:52:23 +00:00
stdlib typo 2013-02-26 12:46:09 +00:00
testsuite add a few more cases 2013-02-26 12:45:45 +00:00
tools Adding extension/attribute on patterns. 2013-03-04 13:52:23 +00:00
toplevel Merge short-paths into a fresh branch of trunk. 2013-01-29 14:21:12 +00:00
typing Adding extension/attribute on patterns. 2013-03-04 13:52:23 +00:00
utils typo 2013-02-26 12:46:28 +00:00
yacc yacc: "ocamlyacc$(EXE)" rule produced "ocamlyacc" (no trailing $(EXE)). 2013-02-25 03:01:26 +00:00
.depend Add warning 42 for disambiguated labels and constructors (compatibility with old versions) 2013-02-19 02:45:09 +00:00
.ignore Add two more entries to .ignore 2012-12-31 01:25:54 +00:00
Changes Labtk now supports 8.6. 2013-02-27 19:31:47 +00:00
INSTALL merge changes from 4.00 branching to 4.00.0 (part 1) 2012-07-26 19:21:54 +00:00
LICENSE merge changes from 3.12.0 to 3.12.1 2011-07-20 09:17:07 +00:00
Makefile Tabify. 2013-02-12 08:14:24 +00:00
Makefile.nt Move ast_mapper to parsing/, make it part of compiler-libs, and add an interface. Plus minor code cleanup. 2013-01-16 16:10:29 +00:00
README remove all $Id keywords 2012-10-15 17:50:56 +00:00
README.win32 merge changes from 4.00 branching to 4.00.0 (part 1) 2012-07-26 19:21:54 +00:00
VERSION PR#5775: several bug fixes for tools/pprintast.ml 2012-10-16 09:51:42 +00:00
_tags Install compiler internals (as libraries + compiled interfaces + start modules) 2012-05-17 16:04:13 +00:00
configure Labtk now supports 8.6. 2013-02-27 19:31:47 +00:00
myocamlbuild.ml remove all $Id keywords 2012-10-15 17:50:56 +00:00
myocamlbuild_config.mli merge with branch bin-annot 2012-05-30 14:52:37 +00:00

README

OVERVIEW:

OCaml is an implementation of the ML language, based on the Caml Light
dialect extended with a complete class-based object system and a
powerful module system in the style of Standard ML.

OCaml comprises two compilers. One generates bytecode which is then
interpreted by a C program. This compiler runs quickly, generates
compact code with moderate memory requirements, and is portable to
essentially any 32 or 64 bit Unix platform. Performance of generated
programs is quite good for a bytecoded implementation.  This compiler
can be used either as a standalone, batch-oriented compiler that
produces standalone programs, or as an interactive, toplevel-based
system.

The other compiler generates high-performance native code for a number
of processors. Compilation takes longer and generates bigger code, but
the generated programs deliver excellent performance, while retaining
the moderate memory requirements of the bytecode compiler. The
native-code compiler currently runs on the following platforms:

Tier 1 (actively used and maintained by the core OCaml team):

    AMD64 (Opteron)    Linux, MacOS X, MS Windows
    IA32 (Pentium)     Linux, FreeBSD, MacOS X, MS Windows
    PowerPC            Linux, MacOS X
    ARM                Linux

Tier 2 (maintained when possible, with help from users):

    AMD64              FreeBSD, OpenBSD
    IA32 (Pentium)     NetBSD, OpenBSD, Solaris 9
    PowerPC            NetBSD
    SPARC              Solaris, Linux, NetBSD

Other operating systems for the processors above have not been tested,
but the compiler may work under other operating systems with little work.

Before the introduction of objects, OCaml was known as Caml Special
Light. OCaml is almost upwards compatible with Caml Special Light,
except for a few additional reserved keywords that have forced some
renaming of standard library functions.

CONTENTS:

  Changes               what's new with each release
  INSTALL               instructions for installation
  LICENSE               license and copyright notice
  Makefile              main Makefile
  README                this file
  README.win32          infos on the MS Windows ports of OCaml
  asmcomp/              native-code compiler and linker
  asmrun/               native-code runtime library
  boot/                 bootstrap compiler
  bytecomp/             bytecode compiler and linker
  byterun/              bytecode interpreter and runtime system
  camlp4/               the Camlp4 preprocessor
  config/               autoconfiguration stuff
  debugger/             source-level replay debugger
  driver/               driver code for the compilers
  emacs/                OCaml editing mode and debugger interface for GNU Emacs
  lex/                  lexer generator
  maccaml/              the Macintosh GUI
  ocamldoc/             documentation generator
  otherlibs/            several external libraries
  parsing/              syntax analysis
  stdlib/               standard library
  tools/                various utilities
  toplevel/             interactive system
  typing/               typechecking
  utils/                utility libraries
  yacc/                 parser generator

COPYRIGHT:

All files marked "Copyright INRIA" in this distribution are copyright
1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006,
2007, 2008, 2009, 2010, 2011, 2012 Institut National de Recherche en
Informatique et en Automatique (INRIA) and distributed under the
conditions stated in file LICENSE.

INSTALLATION:

See the file INSTALL for installation instructions on Unix, Linux and
MacOS X machines.  For MS Windows, see README.win32.

DOCUMENTATION:

The OCaml manual is distributed in HTML, PDF, Postscript, DVI, and
Emacs Info files.  It is available on the World Wide Web, at

        http://caml.inria.fr/

AVAILABILITY:

The complete OCaml distribution can be accessed at

        http://caml.inria.fr/

KEEPING IN TOUCH WITH THE CAML COMMUNITY:

There exists a mailing list of users of the OCaml implementations
developed at INRIA. The purpose of this list is to share
experience, exchange ideas (and even code), and report on applications
of the OCaml language. Messages can be written in English or in
French. The list has more than 1000 subscribers.

Messages to the list should be sent to:

              caml-list@inria.fr

You can subscribe to this list via the Web interface at

        https://sympa-roc.inria.fr/wws/info/caml-list

Archives of the list are available on the Web site above.

The Usenet news groups comp.lang.ml and comp.lang.functional
also contains discussions about the ML family of programming languages,
including OCaml.

BUG REPORTS AND USER FEEDBACK:

Please report bugs using the Web interface to the bug-tracking system
at http://caml.inria.fr/bin/caml-bugs

To be effective, bug reports should include a complete program
(preferably small) that exhibits the unexpected behavior, and the
configuration you are using (machine type, etc).

You can also contact the implementors directly at caml@inria.fr.