May 11, 2009 at 8:47 PM


       I've recently finished migrating to the newest version of Irony and I'm noticing some issues concerning the TokenEditorInfo structure.  Does it really need to exist?  In my Lua editor implementation, I've had to modify the TokenColor enumerations to support "Operators" and "Punctuation".  I've also ran into an issue in which I cannot use the "AutoDetectKeywords" feature of the compiler while still using TokenEditorInfo (because only the flag IsKeyword is set, the TokenEditor information doesn't gets set to Keyword enumerations).  I think ultimately I'll end up using my own variation of an EditorInfo class that is fine tuned for my own editor (since I'll be adding new styles and triggers based on some document object model).



May 11, 2009 at 9:55 PM

No need to panic. I didn't address the VS integration functionality yet, but would be happy to do this. Can you send me your new sources integrated with latest Irony version, with the list of exact issues you're having? I will try to fix them and push the changes into the new version.


May 11, 2009 at 10:06 PM

Disregard my issue about the IsKeyword problem.  I noticed that in my line scanner I was not using the EditorInfo in the AsSymbol member property of a token instead of the EditorInfo itself.  Once I resolved that issue it looks great now :)  So that means that the only current issue is the need to modify the TokenColor enumeration to support new types.

I'll see if I can build a list of some features or tweaks that can be done to better support VS integration.  I had to add some functionality to include support for hidden regions as well as matching multiples and not just matching braces.