Author: Manuel Jacob Branch: improve-docs Changeset: r72582:48825b4cc915 Date: 2014-07-27 23:40 +0200 http://bitbucket.org/pypy/pypy/changeset/48825b4cc915/
Log: Move two paragraphs from architecture.rst to index.rst, which now are used as introductory words (with some modifications). diff --git a/rpython/doc/architecture.rst b/rpython/doc/architecture.rst --- a/rpython/doc/architecture.rst +++ b/rpython/doc/architecture.rst @@ -1,26 +1,6 @@ Goals and Architecture Overview =============================== -.. contents:: - -Mission statement ------------------ - -We aim to provide a common translation and support framework for producing -implementations of dynamic languages, emphasizing a clean separation between -language specification and implementation aspects. We call this the -:doc:`RPython toolchain <translation>`. - -By separating concerns in this way, our implementation -of Python - and other dynamic languages - is able to automatically -generate a Just-in-Time compiler for any dynamic language. It also -allows a mix-and-match approach to implementation decisions, including -many that have historically been outside of a user's control, such as -target platform, memory and -threading models, garbage collection strategies, and optimizations applied, -including whether or not to have a JIT in the first place. - - High Level Goals ---------------- diff --git a/rpython/doc/index.rst b/rpython/doc/index.rst --- a/rpython/doc/index.rst +++ b/rpython/doc/index.rst @@ -1,6 +1,19 @@ Welcome to RPython's documentation! =================================== +RPython is a translation and support framework for producing implementations of +dynamic languages, emphasizing a clean separation between language +specification and implementation aspects. + +By separating concerns in this way, our implementation of Python - and other +dynamic languages - is able to automatically generate a Just-in-Time compiler +for any dynamic language. It also allows a mix-and-match approach to +implementation decisions, including many that have historically been outside of +a user's control, such as target platform, memory and threading models, garbage +collection strategies, and optimizations applied, including whether or not to +have a JIT in the first place. + + Table of Contents ----------------- _______________________________________________ pypy-commit mailing list pypy-commit@python.org https://mail.python.org/mailman/listinfo/pypy-commit