RE: [PHP-LANG] Approaching the First Draft [of a language spec]

What is our target audience for the language specification.  I'm familiar
with bison and I'm sure most of the other people who develop PHP and discuss
the specific issues of PHP (in regards to the development of PHP) are as
well.  What about people who are just PHP developer's, how can they have
access to that language specification?  Perhaps we should consider making
the language specification more of something that everyone can understand?

The semantics portion looks pretty good (probably because its so detailed,
it hardly leaves anything up to the imagination ;).

-Sterling


-----Original Message-----
From: Sascha Schumann [mailto:[email protected]]
Sent: Tuesday, November 21, 2000 12:29 AM
To: [email protected]
Subject: [PHP-LANG] Approaching the First Draft [of a language spec]


    Hi all,

    we need a clear roadmap on how to approach the goal of having
    a language specification. Here is the earlier proposal I sent
    to php-dev.

    Note that this does not say anything about the format of the
    final documentation. Your opinions and ideas are welcome.

    Task 1: Defining the syntax

        The syntax can be represented in the common pseudo-grammar
        style, which has been used by K&R and many ANSI/ISO language
        standards before. Everyone who is familiar with Yacc/Bison
        will immediately recognize it. The file `Language_Notation.txt'
        contains a definition and examples.

    Task 2: Defining the semantics

        This comes down to defining what meaning the various pieces of
        the syntax have and what actions they cause.

    The First Draft will be based upon the language implementation
    which is used by PHP 4. The draft may differ from that implementation,
    if the workgroup decides so.

    Thanks,
    - Sascha


--
PHP Language Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
To contact the list administrators, e-mail: [email protected]