I actually hadn't implemented the TokenFilter solution before deciding not to go with that solution, so didn't have any benchmark.
But eventually I have taken care of this problem with a different variation of your quick and dirty solution. I have captured the character '@' in FastCharStream.java, and replaced it with a blank space. That took care of it. Thanks for your help! Tareque > 20 dec 2007 kl. 22.32 skrev [EMAIL PROTECTED]: > >> In fact I had previously located the grammar in StandardTokenizer.jj >> (just wasn't sure if that was the one u were talking about) and had >> commented out EMAIL entries from all the following files: >> >> StandardTokenizer.java >> StandardTokenizer.jj >> StandardTokenizerConstants.java >> >> Now what is puzzling to me is that though I don't see the '@' > > I think you'll find the JavaCC-list a much better forum for this > question. You do however seem a bit confused about the fact that > StandardTokenizer and StandardTokenierConstants are the generated > artifacts via Ant build, based on StandardTokenizer.jj. > > Why was the TokenFilter solution not good enough? What was the results > from your benchmarks? > > > -- > karl > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
