SketchyLISP is a small, tail-recursive, lexically scoped interpreter for
purely symbolic dialect of LISP that smells like Scheme. It may be considered
an implementation of pure LISP plus DEFINE and CALL/CC.
This package contains the SketchyLISP interpreter and library, the reference
manual, and example programs.
WWW: http://www.t3x.org/sketchy/
PR: ports/81012
Submitted by: Nils M Holm <nmh@t3x.org>
the features that people like so much in languages like Python, Ruby and
Smalltalk, making them available to Java developers using a Java-like syntax.
Groovy is designed to help you get things done on the Java 2 Platform in a
quick, concise and fun way. Groovy brings the power of a scripting language
directly into the Java 2 Platform. For example:
- Shell scripting using Groovy allows the full power of the Java Platform to be
brought to bear to the task at hand.
- Groovy can be used (and indeed is already being used) as a replacement for
Java for small and medium sized applications to execute on the Java 2
Platform.
- Groovy can be used as an embedded language for dynamic business rules or
extension points utilizing the agility of Groovy and saving the cost of
redeploying applications for each change of rule (especially when the rules
are stored in a database).
- Groovy makes writing test cases for unit tests very easy.
As well as being a powerful language for scripting Java objects, Groovy can be
used as an alternative compiler to javac to generate standard Java bytecode to
be used by any Java project.
WWW: http://groovy.codehaus.org/
dropped and the lang/ruby16_r and lang/ruby18_r ports have been
removed, since no one seems to appreciate the partially working
solution.
Good news is that the pthread support of lang/ruby18 is now enabled by
default for newer systems, which means the ruby interpreter is linked
with libpthread. This will allow threaded extension libraries to run
and work properly on those systems.
The --march=cputype flag is disabled because it gets ruby to
malfunction and fail to build. I don't know if the problem is in
libpthread or in gcc.
(It really makes me wonder if they had actually tested before asking
me to do this somewhat risky change ;-)
JavaScriptCore is part of Gtk-Wecore.
JavaScriptCore is javascript interpreter that OSB uses. It is based on
Apple's WebCore JavaScriptCore code, which is in turn based on KDE kjs
code.
code with Lua. Based on a "cleaned" header file, toLua automatically
generates the binding code to access C/C++ features from Lua. Using
Lua-5.0 API and tag method facilities, the current version automatically
maps C/C++ constants, external variables, functions, namespace,
classes, and methods to Lua. It also provides facilities to create
Lua modules.
WWW: http://www.tecgraf.puc-rio.br/~celes/tolua/
Author: Waldemar Celes <celes@tecgraf.puc-rio.br>
code with Lua. Based on a "cleaned" header file, toLua automatically
generates the binding code to access C/C++ features from Lua. Using
Lua-5.0 API and tag method facilities, the current version automatically
maps C/C++ constants, external variables, functions, namespace,
classes, and methods
WWW: http://www.tecgraf.puc-rio.br/~celes/tolua/
The asn1c compiles ASN.1 (Abstract Syntax Notation One)
specifications into the C source code. This compiler supports
automatic constraints checking code generation, parametrization,
basic support for Information Object Classes. The produced C code
contains the codecs for BER & DER encoding rules.
PR: ports/71560.
Submitted by: Lev Walkin <vlm@lionet.info>
ANSI-C compiler that targets the Intel 8051, Maxim 80DS390 and the Zilog
Z80 based MCUs.
PR: ports/66262
Submitted by: Tijl Coosemans <tijl@ulyssis.org>
The libjit library implements Just-In-Time compilation
functionality. Unlike other JIT's, this one is designed to be
independent of any particular virtual machine bytecode format
or language. The hope is that Free Software projects can get a
leg-up on proprietry VM vendors by using this library rather
than spending large amounts of time writing their own JIT from
scratch.
This JIT is also designed to be portable to multiple
archictures. If you run libjit on a machine for which a native
code generator is not yet available, then libjit will fall back
to interpreting the code. This way, you don't need to write
your own interpreter for your bytecode format if you don't want
to.
PR: ports/66038
Submitted by: michael johnson <ahze@ahze.net>
