String variable constants are not highlighted

[wmysterio]

{$CLEO .cs}
0000:

const

handle = 10@

my_strs1 = 20@s   
my_strs2 = s$str

my_strv1 = 6@v
my_strv2 = v$str

end

0A93: terminate_this_custom_script

[x87]

@wmysterio Do you expect my_str* to be blue (as variables) or red (as strings)?

[wmysterio]

@x87 This is a report from Vital. As far as I understood, blue is expected. Color for variables, as in handle = 10@ case.

[VitalRus95]

Sorry for having @wmysterio send this report instead of me, I was rather busy and only got rid of some routine now.
I may add that not only string constants, but also expressions constants are not highlighted, both in semantic and non-semantic modes. As for the colour, I expect it to follow the highlighting mode: if it's the semantic one, then strings should be the string colour if it's possible.

How the issue looks in my case:

[x87]

@VitalRus95 try with this version (unzip to SB\lib)
core.zip

sanny should highlight them as variables (blue).

expressions constants are not highlighted

they probably should not. what color do you expect?

[VitalRus95]

@x87, thank you, that makes the highlighter see the string constants! Now I also can select them from the list (Ctrl+Space), and I wasn't able to before your fix.
As for expressions constants, they are still not highlighted at all and not present in the pop-up list. If possible, I think the colour can match the class commands' colour. Thank you once again for your help!

[x87]

expressions constants, they are still not highlighted at all and not present in the pop-up list.

to be fair, I think this is a quirk in the language and should be avoided. By no means actor.Angle(plr) is a constant.

[wmysterio]

By no means actor.Angle(plr) is a constant.

This entry looks more like some kind of macro than a constant in the usual sense.