| [cdt-dev] IType and @noextend |
|
Hi guys, Looking at IType in CVS it seems to have gained an @noextend
and an @noimplement and the only implementations appear to be internal, so
shouldn’t be used. Indeed looking at other code a lot of the public
interfaces appear to have gained @noextend (e.g. ICBasicType, ICPPBasicType, IASTNode,
IASTTranslationUnit, ICASTCompositeTypeSpecifier etc). Is the intention that
there should be only the default CDT implementation of these? We’re currently implementing our own AbstractLanguage and
have been carefully avoiding using internal code which means having to
implement our own versions of all of these interfaces. Is creating a new
language not supported in CDT 6.0? Is there some other way that this should be
done? Cheers, Richard
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. |
