http://blog.centuryminds.com/2008/09/antlr-tutorial-dependency-injection-language/ Mon, 21 May 2012 01:10:08 +0000 http://wordpress.org/?v=2.6.2 http://blog.centuryminds.com/2008/09/antlr-tutorial-dependency-injection-language/#comment-207 Good ANTLR Resource - Adam Jordens@littlesquare:~/ Sat, 13 Sep 2008 06:02:18 +0000 http://blog.centuryminds.com/?p=60#comment-207 [...] of others, if you’re looking to get started with ANTLR, here’s a useful introduction blog post. A quick search on dzone would have saved some trial and [...] [...] of others, if you’re looking to get started with ANTLR, here’s a useful introduction blog post. A quick search on dzone would have saved some trial and [...]

]]> http://blog.centuryminds.com/2008/09/antlr-tutorial-dependency-injection-language/#comment-206 kanthi swaroop Thu, 11 Sep 2008 23:10:13 +0000 http://blog.centuryminds.com/?p=60#comment-206 Now thats interesting. Typical applications of ANTLR would be in parsing domain. My first interaction with ANTLR was for a data generation application. We had this system which consume huge xml streams. The schema types were defined via xsi and testing the code for all conditions was inhumane! Even coming up with data for functional flows was painful. So the solution was to comeup with a template of the xml (using schema) and another template for possible datatypes. Parse the template, create a inmemory tree and walk the tree several times (using custom java code). We picked up a random domain value for substitution for each walk and ended up having a comprehensive data sets. There were certain correlation problems though and it was a different story. I really wish, you wrote the article back then ;) Now thats interesting. Typical applications of ANTLR would be in parsing domain. My first interaction with ANTLR was for a data generation application. We had this system which consume huge xml streams. The schema types were defined via xsi and testing the code for all conditions was inhumane! Even coming up with data for functional flows was painful. So the solution was to comeup with a template of the xml (using schema) and another template for possible datatypes. Parse the template, create a inmemory tree and walk the tree several times (using custom java code). We picked up a random domain value for substitution for each walk and ended up having a comprehensive data sets. There were certain correlation problems though and it was a different story. I really wish, you wrote the article back then

]]>