| RE: [cdt-dev] Reusing parser tests |
|
Mike, Sounds like you’ll be working on
exactly the sort of thing I’d need. I’ll try and have a look at the
lrparser test plugin in the next day or so to see what you’ve done - I
assume that’s in CVS. The ILanguage I’m adding is based on
the C/C++ parser from EDG. Our commercial product ( We have a user interface for this that is
based on Eclipse/CDT but a problem we’ve seen is that customers have code
that uses language extensions that works with our parser and their compiler but
causes problems for the CDT GNU parser. This isn’t really surprising as gcc
won’t accept it either, but it is an issue for our customers. In addition we provide the ability to
generate and edit test scripts, but this is based on a combination of
information produced by our tool at compile time and information gleaned from the
AST. With my ILanguage implementation every IASTNode can contain additional
data that is useful to us and we wouldn’t have to rely on the files
generated at compile time. This would be a big plus for us as there are
situations where the way the EDG parser describes an item doesn’t
necessarily match to the way it is in the AST. The theory is that If we can get our
parser into Eclipse then everything should ‘just work’. Unfortunately
the structure of the EDG Intermediate Language doesn’t closely match the
AST all the time and EDG parser is written in C so there’s a nice JNI
layer involved. The question of how far I am through
implementing it is a tricky one; I’m further through C than C++ but
testing it is a little tricky. The main reason I want to try reusing the
existing CDT tests is to give myself a better idea of what I’m missing. Also
I’ve not attempted to support code completion yet. Cheers, Richard From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mike Kucera I'm reusing many of the tests for my own ILanguage
implementation. Its pretty cumbersome at the moment, because the tests don't
actually call the parser through ILanguage. Instead they call the CDT core
parser directly. The way I was able to reuse the tests was to subclass each one
individually and override whatever parse() method the test has. Take a look in
the lrparser test plugin to see how it works.
The information transmitted is intended only
for the person or entity to which it is addressed and may contain confidential
and/or privileged material. If you are not the addressee, any disclosure,
reproduction, copying, distribution, or other dissemination or use of this
communication is strictly prohibited. If you have received this transmission in
error please notify the sender immediately and then delete this email.
Any representations or commitments expressed
in this email are subject to contract. This message has been scanned for viruses and
dangerous content. However, it is essential that the recipient also checks this
message using commercially available mail scanning and anti-virus software. IPL
Information Processing Limited accepts no liability for any loss or damage
resulting from any virus or other dangerous content in this message.
IPL Information Processing Limited is
registered in The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this email. Any representations or commitments expressed in this email are subject to contract. This message has been scanned for viruses and dangerous content. However, it is essential that the recipient also checks this message using commercially available mail scanning and anti-virus software. IPL Information Processing Limited accepts no liability for any loss or damage resulting from any virus or other dangerous content in this message. IPL Information Processing Limited is registered in England and Wales under company registration number 1418818. Registration took place at Cardiff on 10 May 1979. IPL Information Processing Limited's registered office and normal place of business is Eveleigh House, Grove Street, Bath, BA1 5LR, United Kingdom. IPL is also registered for Value Added Tax (VAT) under registration number GB 601 2931 83. |
