Final Programming Assignment: bnf grammar Syntax Internet and Intranet Protocols and Applications
Download 16.13 Kb.
|
Final Programming Assignment: BNF Grammar SyntaxInternet and Intranet Protocols and ApplicationsSpring 2003 Prof. Arthur P. Goldberg (Thanks to Jeremy Weinberger) This is at http://www.cs.nyu.edu/artg/internet/Spring2003/assignments/IMAP_BNF_Grammar_Syntax.doc
notation. The differences from standard BNF involve naming rules and indicating repetition and "local" alternatives.
name of a rule is simply the name itself, rather than " Quotation-marks enclose literal text (which may be upper and/or lower case). Certain basic rules are in uppercase, such as SPACE, TAB, CRLF, DIGIT, ALPHA, etc. Angle brackets are used in rule definitions, and in the rest of this document, whenever their presence will facilitate discerning the use of rule names.
fore "foo / bar" will accept foo or bar. 2.3. (RULE1 RULE2): LOCAL ALTERNATIVES Elements enclosed in parentheses are treated as a single element. Thus, "(elem (foo / bar) elem)" allows the token sequences "elem foo elem" and "elem bar elem".
The full form is: indicating at least Default values are 0 and infinity so that "*(element)" allows any number, including zero; "1*element" requires at least one; and "1*2element" allows one or two. 2.5. [RULE]: OPTIONAL Square brackets enclose optional elements; "[foo bar]" is equivalent to "*1(foo bar)". 2.6. NRULE: SPECIFIC REPETITION " exactly number, and 3ALPHA is a string of three alphabetic characters.
by one or more commas (","). This makes the usual form of lists very easy; a rule such as '(element *("," element))' can be shown as "1#element". Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is, "(element),,(element)" is permitted, but counts as only two elements. Therefore, where at least one ele- ment is required, at least one non-null element must be present. Default values are 0 and infinity so that "#(element)" allows any number, including zero; "1#element" requires at least one; and "1#2element" allows one or two.
2.7 (LISTS) is revised for IMAP. In the IMAP RFC (2060), list elements are separated by a single space, NOT commas. ***(jjw)
text, starts a comment that continues to the end of line. This is a simple way of including useful notes in parallel with the specifications. Download 16.13 Kb. Share with your friends:
|