Transformation of Applicative Specifications into Imperative ...

APPENDIX E. ANTLR GRAMMAR
}
: ’ . ’ { _ttype = DOT; }
|
(
’ 0 ’
// s p e c i a l case f o r j u s t ’ 0 ’
|
( ’ 1 ’ . . ’ 9 ’ ) ( ’ 0 ’ . . ’ 9 ’ ) ∗
// non−zero decimal
)
( ( ’ . ’ ( ’ 0 ’ . . ’ 9 ’ )+) =>
( ’ . ’ ( ’ 0 ’ . . ’ 9 ’ )+)
{_ttype = REAL_LITERAL; }
) ?
;
IDENT
options { t e s t L i t e r a l s=true ; }
: ( ’ a ’ . . ’ z ’ | ’A ’ . . ’Z ’ )
( ’ a ’ . . ’ z ’ | ’A ’ . . ’Z ’ | ’_ ’ | ’ 0 ’ . . ’ 9 ’ ) ∗
;
WS
: ( ’ ’
| ’ \ r ’ ’ \n ’ { newline ( ) ; }
| ’ \n ’ { newline ( ) ; }
| ’ \ t ’
)
{ $setType ( Token . SKIP) ; }
;
// m u l t i p l e −l i n e comments
ML_COMMENT
: "/∗"
(
/∗
’\ r ’ ’ \ n ’ can be matched in one a l t e r n a t i v e or by matching
’\ r ’ in one i t e r a t i o n and ’\ n ’ in another . I am t r y i n g to
handle any f l a v o r o f newline t h a t comes in , but the language
t h a t a l l o w s both "\ r \n " and "\ r " and "\n" to a l l be v a l i d
newline i s ambiguous . Consequently , the r e s u l t i n g grammar
must be ambiguous . I ’m s h u t t i n g t h i s warning o f f .
∗/
options {
generateAmbigWarnings=f a l s e ;
}
:
{ LA( 2 ) != ’ / ’ } ? ’ ∗ ’
| ’ \ r ’ ’ \n ’ { newline ( ) ; }
506