[pypy-svn] rev 1959 - pypy/trunk/doc/funding
pedronis at codespeak.net
pedronis at codespeak.net
Wed Oct 15 14:17:33 CEST 2003
Author: pedronis
Date: Wed Oct 15 14:17:32 2003
New Revision: 1959
Modified:
pypy/trunk/doc/funding/B1.0_objectives.txt
Log:
added more contrast between our approach and Scheme 48, Squeak.
Mentioned abstract interp and its pluses.
Modified: pypy/trunk/doc/funding/B1.0_objectives.txt
==============================================================================
--- pypy/trunk/doc/funding/B1.0_objectives.txt (original)
+++ pypy/trunk/doc/funding/B1.0_objectives.txt Wed Oct 15 14:17:32 2003
@@ -92,13 +92,18 @@
In its basics, the approach of writing a language interpreter in the
language itself (a subset thereof) and then producing a running
low-level code version trough a translation process has already been
-taken, e.g. for the Scheme (Scheme 48) [K97]_ and the
-Smalltalk (Squeak) [IKM97]_ languages. Obtaining in this
-way an interpreter comparable with current C Python implementation is
-within current state of the art, but we plan to exploit
-the gained flexibility much further, separating concerns between the
-translator, the code and Object Spaces encapsulating the core language
-and its semantics and further pluggable modules for both.
+taken, e.g. for the Scheme (Scheme 48) [K97]_ and the Smalltalk
+(Squeak) [IKM97]_ languages. These approaches are typically based on
+translation from high-level source code parsed into ASTs to
+C. Obtaining in this way an interpreter comparable with current C
+Python implementation is within current state of the art, but we plan
+to exploit the gained flexibility much further, separating concerns
+between the translator, the code and Object Spaces encapsulating the
+core language and its semantics and further pluggable modules for
+both. We intend to use abstract interpretation as our analysis tool
+making the Object Space operations the semantics units also for
+translation, leveraging the coherence of our architecture and gaining
+independence from surface issues.
Haskell monadic modular interpreters [LHJ95]_ [H98]_ are a
researched attempt at achieving modularity for interpreters. They have
More information about the Pypy-commit
mailing list