#943 Additional LexCPP keyword classes


For richer syntax coloring in FlashDevelop we have patched LexCPP to add 3 additional keyword classes. It takes time to keep our fork in sync with Scintilla updates so I'm asking you to include it by default.


  • Neil Hodgson

    Neil Hodgson - 2012-06-06

    Why is 3 the correct number of additional keyword lists? Why is this better than 2? Or 4?

  • Neil Hodgson

    Neil Hodgson - 2012-06-06
    • assigned_to: nobody --> nyamatongwe
    • priority: 5 --> 2
    • milestone: --> Won't_Implement
  • Philippe

    Philippe - 2012-06-07

    I'm open to implement it differently - would you accept it if it's based on a property defining an arbitrary number of additional keyword lists?

  • Neil Hodgson

    Neil Hodgson - 2012-06-09

    That would increase divergence between stand-alone JavaScript and JavaScript in HTML. It would also make a more complete solution difficult. A better solution would allow each type of keyword (for HTML: tags, attributes, PHP keywords, JavaScript keywords, ...) to output multiple styles.

  • Philippe

    Philippe - 2012-06-09

    The goal isn't to add more keywords to JS, but to support more subtle coloring of more complex languages using the cpp lexer (Actionscript, Haxe). This was a popular request among our users who love to completely customize their colors.

    But I suppose it'll be better to make this aspect more flexible in scintilla general instead of this kind of monkey patching.

  • Neil Hodgson

    Neil Hodgson - 2013-02-26

    There is now provisional support for substyles in the C++ lexer so they can be experimented with. Provisional means it may change before becoming final.

  • Neil Hodgson

    Neil Hodgson - 2014-05-09
    • labels: --> scintilla, lexer, cpp
    • status: open --> closed
  • Neil Hodgson

    Neil Hodgson - 2014-05-09

    Substyles are now finalized so should be used for this case.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks