What's the order of priority for Generic Tokens?

I’m having trouble getting the string to tokenize properly because certain rules take precedence over others resulting in misclassification.

Is it the Generic Token Type and then the enum value? Or is it the highest enum value that gets tokenized first?

public enum StdToken
   {

       [Keyword("XL")]
       [Push("xlmode")]
       START_X = 100,        

       [Sugar("@")]
       [Push("dmode")]
       START_D = 101,
 
       [Lexeme(GenericToken.UpTo, ">>", "\0")]
       [Mode("dmode", "xlmode")]
       [Pop]
       OPS = 103,

       [Sugar(">>")]
       INSTALL = 15,

       [Sugar("(")]
       LPAREN = 40,

       [Sugar(")")]
       RPAREN = 41,

       [Keyword("Int")]
       [Keyword("String")]
       [Keyword("Optset")]
       [Keyword("Money")]
       [Keyword("Decimal")]
       [Keyword("EtnRef")]
       CONVERT = 104,

       [Sugar(":")]
       COLON = 105,
   }

Given the following: “XL(Key Metrics/C455) >> String: @working_adj.amount”,

It’s coming out as START_X OPS INSTALL CONVERT OPS - the last OPS tokenized as “: @working_adj.amount”

when it should be: START_X OPS INSTALL CONVERT COLON START_D OPS

[b3b00]

thanks again for reporting @TamaBaka. I guess you are the first csly user to try the lexer modes feature using keywords are mode triggers.

[b3b00]

@TamaBaka version 2.9.3.0 is now published. It solves your issue. Could you try and tell me if it’s ok for you ?