RE: [PHP-LANG] Approaching the First Draft [of a language spec]
[email protected] (Derick Rethans)
| Newsgroups | php.lang |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 21 Nov 2000, Sascha Schumann wrote: > On Tue, 21 Nov 2000, Derick Rethans wrote: > > > > > On Mon, 20 Nov 2000, Sterling Hughes wrote: > > > > > > I'm not sure how the end-user will be able to benefit from a > > > > list of syntactical rules. Can you elaborate what you have in > > > > mind? > > > > > > I find myself most often reading the source of PHP when I want an answer to > > > a question regarding syntax rather than going to the documentation. I think > > > it would be great for the end user to have a syntax sheet showing them what > > > is legal PHP and what isn't legally PHP as both a reference and as learning > > > tool. It also is a way of guaranteeing the users "this will work", this is > > > valid PHP syntax and this won't work, this is not valid syntax. > > > > So if I can see, the result of this project will be the > > zend_language_parser.y, stripped from all actions and constructs to make > > yacc happy. > > As I already said in private email that it is incorrect. A > grammar (Task 1 of the proposal) is the sum of the parser > and the lexer. A, then I misunderstood you... this will indeed be very usefull. > > > I think this is pretty useless if there is not given a > > semantical meaning for these rules. What do you have in mind about this > > Sascha (or give a small example of what you mean)? > > Please refer to Task 2. > Derick