| RE: [cobol-dev] COBOL plugin & COBOL parsing |
Hello Jens, Thanks for your reply. I found the code on the website :) When I asked what dialects would be supported I was referring to the plentitude of dialects of COBOL supported out there, so "mainframe COBOL" is not 100% specific unless I'm missing something (e.g. IBM, Micro Focus, Microsoft, Ryan McFarland, Fujitsu, etc.etc.) "why take it away from here?" - I assume you mean, why would I want to use the COBOL parser as an API that is not tightly coupled with the rest of the Eclipse framework. This is because the requirements of my project are such that I need to be able to invoke a COBOL parser and have full access to the AST tree it generates, in Java. This particular project I am working on is not slated to become an Eclipse plugin, it is a part of our server. So, ideally, I'd love to be able to pass a java.io.File pointing at a COBOL source file, into an API that simply returns the AST tree or lets me plug in a visitor class that would walk that tree. Is such a capability something that is difficult to add? Would you consider adding it in the near future? It would be very useful! Thanks! - Dmitry ________________________________ From: cobol-dev-bounces@xxxxxxxxxxx on behalf of jd@xxxxxxxxx Sent: Mon 7/23/2007 11:37 AM To: Development discussions about the COBOL IDE for Eclipse. Subject: Re: [cobol-dev] COBOL plugin & COBOL parsing Hello Dmitry, these features are planned: a) what language does the plugin support? mainframe COBOL b) are embedded SQL, CICS and DLI supported? yes c) is the source code for the plugin downloadable or will it be? no reply d) is the javadoc of the plugin classes available? no reply e) does the COBOL parser that the plugin have expose the ability for its caller to invoke it from outside of the plugin framework and use it as an API? why take it away from here? Regards Jens _______________________________________________ cobol-dev mailing list cobol-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cobol-dev
<<winmail.dat>>