[pypy-svn] r3542 - pypy/trunk/doc/funding
arigo at codespeak.net
arigo at codespeak.net
Wed Mar 31 00:24:18 CEST 2004
Author: arigo
Date: Wed Mar 31 00:24:18 2004
New Revision: 3542
Modified:
pypy/trunk/doc/funding/B1.0_objectives.txt
pypy/trunk/doc/funding/B6.0_detailed_implementation.txt
pypy/trunk/doc/funding/B6.7.wp13_integration_config.txt
Log:
Rephrase "user" to "language user".
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 Mar 31 00:24:18 2004
@@ -6,7 +6,8 @@
---------------------------
Current language implementations are static and hard to modify by
-users. Even the implementations of open-source dynamic languages have
+programmers that use them ("language users").
+Even the implementations of open-source dynamic languages have
non-flexible designs crafted by a small group of developers. While
designing a good programming language is no easy task, often
application developers seek more support and configurability of their
@@ -53,7 +54,7 @@
encapsulates computational operations on objects, separated from the
bytecode interpreter. A number of features, most of which are hard to
implement as application-level libraries, can become part of the
-language in a manageable and user-configurable way if they are
+language in a manageable and language-user-configurable way if they are
implemented modularly as Object Spaces. For example:
* choice of memory and threading model
@@ -249,8 +250,9 @@
direct translation.
Finally we expect to develop automatic interpreter build tools that allow
-choices about aspects, predefined or user-supplied modifications
-and extensions to be made from the language user.
+choices about aspects, modifications and extensions to be made by the
+language user, and that enable advanced programmers to develop and
+integrate their own aspects and extensions to the language.
----------------------------------------------
Modified: pypy/trunk/doc/funding/B6.0_detailed_implementation.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.0_detailed_implementation.txt (original)
+++ pypy/trunk/doc/funding/B6.0_detailed_implementation.txt Wed Mar 31 00:24:18 2004
@@ -422,8 +422,8 @@
It is expected that most of the applications described above will still be
relatively experimental when the project ends. It is also expected that the
-extreme flexibility will lead to a potentially large number of different
-end-user configurations of PyPy. Thus our essential goal, beyond validating
+extreme flexibility will lead to the deployment of a potentially large number
+of different configurations of PyPy. Thus our essential goal, beyond validating
our techniques and showing what can be done and how it benefits from
integration with the language, is to make this knowledge available and
easy-to-use for contributors and third-parties.
Modified: pypy/trunk/doc/funding/B6.7.wp13_integration_config.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.7.wp13_integration_config.txt (original)
+++ pypy/trunk/doc/funding/B6.7.wp13_integration_config.txt Wed Mar 31 00:24:18 2004
@@ -58,7 +58,7 @@
**Milestones and Expected Result**
-- A stable release of PyPy enabling a wide range of users to
+- A stable release of PyPy enabling a wide range of language users to
experiment and develop using it as a flexible and highly-optimizable
Python implementation.
More information about the Pypy-commit
mailing list