forked from Lainports/freebsd-ports
b51d447684
are unsafe by default, which is the main motivation why it was picked,
but not the very latest one) and synchronize the rest of the stack and
dependent ports with it, particularly:
- Update `devel/ocaml-ocamlbuild' to version 0.14.0 and unbreak,
register build dependency on all ports that require it (should
be part of USE_OCAML, but we do not want to make any Mk-related
changes the for time being)
- Update `devel/ocaml-camlp4' to version 4.05+2
- Update `devel/ocaml-camlp5' to version 7.07 (the project had
moved to GitHub)
- Mark `devel/ocaml-deriving-ocsigen' as BROKEN for now, it is
very outdated and requires quite a lot of work
- Update `x11-toolkits/ocaml-labltk' to version 8.06.3
PR: 218333
Exp-run by: antoine
19 lines
1,022 B
Text
19 lines
1,022 B
Text
Objective Caml 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.
|
|
|
|
Objective Caml 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:
|
|
almost twice as fast as Caml Light 0.7. 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.
|
|
|
|
WWW: http://ocaml.org/
|