Joseph Kesselman/CAM/Lotus wrote: > If you don't like the terms "parser" (for fear of confusion with XML > parser) or "compiler" (for fear of confusion with > compilation-to-executable)... how about stepping outside the box and > finding a synonym such as "scanner"? I've seen that one used in the past
Scanner implies that it's doing little more than tokenizing the native format of the grammar file. > for code which was something between a tokenizer and a parser... It might > not be the best term, but it at least dodges the two obviou pitfalls. > > Or "GrammarBuilder", which is both more general and more specific... Perhaps "*Builder" or "*Loader" are more appropriate afterall. I prefer the latter just because it seems to imply loading from a stream as opposed to building out of thin air, as an example. -- Andy Clark * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
