Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.compilers > #2416
| From | Kaz Kylheku <493-878-3164@kylheku.com> |
|---|---|
| Newsgroups | comp.compilers |
| Subject | Re: Segmentation in programming language grammars .. why? |
| Date | 2019-12-30 18:04 +0000 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <19-12-035@comp.compilers> (permalink) |
| References | <19-12-034@comp.compilers> |
On 2019-12-30, rockbrentwood@gmail.com <rockbrentwood@gmail.com> wrote: > and is segmented into subgroups Sx, Sc, Se, Sb, Sl, Sj of S. Why? Why not just > write it as one segment like this? It's not creating new conflicts in so > doing. They want to maintain hierarchical categories like "iteration statement" and "selection statement" as part of the language definition. There is some advantage in this when documenting, because the grammar fragment given in each section is understood to be complete. That is to say, in the document section on selection statements, say, the grammar fragment which defines selection-statement is complete in the sense that nothing else in the document is a selection-statement.
Back to comp.compilers | Previous | Next — Previous in thread | Find similar
Segmentation in programming language grammars .. why? rockbrentwood@gmail.com - 2019-12-29 21:05 -0800 Re: Segmentation in programming language grammars .. why? Kaz Kylheku <493-878-3164@kylheku.com> - 2019-12-30 18:04 +0000
csiph-web