RE: [cdt-dev] add new keyword recognize by the dom parser

[Mike Kucera <mkucera@xxxxxxxxxx>]

Are you using different ILanguages for the header and source files? I wonder if thats causing your problems.

I can't tell you weather the new LR parsers would help you solve this issue, because I'm not really sure what the issue is. Can you describe your setup in more detail. How different is POPC++ from regular C++? Is parclass just a keyword that can go wherever the class keyword normally goes, or is there extra syntax associated with it as well?



Mike Kucera
Software Developer
IBM Eclipse CDT Team
mkucera@xxxxxxxxxx

Christian Wiederseiner ---06/12/2008 08:55:36 AM---hello,

From:	Christian Wiederseiner <christian.wiederseiner@xxxxxxxxxxx>
To:	cdt-dev@xxxxxxxxxxx
Date:	06/12/2008 08:55 AM
Subject:	RE: [cdt-dev] add new keyword recognize by the dom parser

---

hello,

thank you for your answer

So the comportement is a bit strange.

1. with semantic highlighting on :
- wenn I open the file the colored @{ as never the color

- wenn I just edit the @{... part.  For example delete the @ and put it
again, the color come back 
(Then if I close and then open the file again no color is visible)

2. without semantic highlighting :
- wenn I open the file the colored @{ part as the right color




An other big issue I found, and I believe it would be difficult to change
the behavior to make it work. 

In the  POPC++ language the parclass keyword is used in .ph file. Those
files are header file, so they will be used as include. For example :
#include "MatWorker.ph"
1. In case no file include the MatWorker.ph, the outline view for the
MatWorker.ph as the green icon class, with the detailed content of
functions/attributs
2. In case one file include the MatWorker.ph, the outline view for the
MathWorker.ph as no more the green icon class, and the detailed content as
disapear.

My question is : would the C99 project (like in UPC) help to resolve such an
issue. I read that UPC use new types for some keywords. But this is not
really related to type, because parclass is now mapped to
IToken.t_classtype. 

Does a similar problem has been resolve for UPC.

Thank you for your time,

-- 
View this message in context: http://www.nabble.com/add-new-keyword-recognize-by-the-dom-parser-tp17621864p17799337.html
Sent from the Eclipse CDT - Development mailing list archive at Nabble.com.

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev