category: reflective

`Description:`	from Rainer Joswig (rainer@ki6.informatik.uni-hamburg.de) : To make it short: Reflective Languages have access to their own implementation. One can ask about the state of the running system and/or change aspects of the language.

`Language:`	ABCL/1 (An object-Based Concurrent Language)
`Package:`	ABCL/1
`Version:`	?
`Parts:`	?
`Author:`	Akinori Yonezawa, ABCL Group now at Department of Information Science, the University of Tokyo
`Location:`	ftp://camille.is.s.u-tokyo.ac.jp/pub/abcl1/*
`Description:`	Asynchronous message passing to objects.
`Reference:`	"ABCL: An Object-Oriented Concurrent System", Edited by Akinori Yonezawa, The MIT Press, 1990, (ISBN 0-262-24029-7)
`Restriction:`	no commercial use, must return license agreement
`Requires:`	Common Lisp
`Contact:`	abcl@is.s.u-tokyo.ac.jp
`Updated:`	May 23rd, 1990

`Language:`	ABCL ???
`Package:`	ABCL/R2
`Version:`	?
`Parts:`	?
`Author:`	masuhara@is.s.u-tokyo.ac.jp, matsu@is.s.u-tokyo.ac.jp, takuo@is.s.u-tokyo.ac.jp, yonezawa@is.s.u-tokyo.ac.jp
`Location:`	ftp://camille.is.s.u-tokyo.ac.jp/pub/abclr2/*
`Description:`	ABCL/R2 is an object-oriented concurrent reflective language based on Hybrid Group Architecture. As a reflective language, an ABCL/R2 program can dynamically control its own behavior, such as scheduling policy, from within user-program. An an object-oriented concurrent language, this system has almost all functions of ABCL/1.
`Requires:`	Common Lisp
`Updated:`	January 28th, 1993

`Language:`	MeldC (MELD, C)
`Package:`	MeldC
`Version:`	2.0
`Parts:`	microkernel, compiler, debugger, manual, examples
`Author:`	MELD Project, Programming Systems Laboratory at Columbia University
`Location:`	obtain license from <MeldC@cs.columbia.edu>
`Description:`	MeldC 2.0: A Reflective Object-Oriented Coordination Programming Language MELDC is a C-based, concurrent, object-oriented language built on a reflective architecture. The core of the architecture is a micro-kernel (the MELDC kernel), which encapsulates a minimum set of entities that cannot be modeled as objects. All components outside of the kernel are implemented as objects in MELDC itself and are modularized in the MELDC libraries. MELDC is reflective in three dimensions: structural, computational and architectural. The structural reflection indicates that classes and meta-classes are objects, which are written in MELDC. The computational reflection means that object behaviors can be computed and extended at runtime. The architectural reflection indicates that new features/properties (e.g., persistency and remoteness) can be constructed in MELDC.
`Restriction:`	must sign license, cannot use for commercial purposes
`Ports:`	Sun4/SunOS4.1 Mips/Ultrix4.2
`Contact:`	<MeldC@cs.columbia.edu>
`Updated:`	December 15th, 1992

This work supported by Idiom Consulting. Idiom is a full-service ISP, providing Internet access in Northern California and Web hosting worldwide.

The HTML is maintained by David Muir Sharnoff and the entries themselves are currently maintained by Bryan Miller.