Const difference between dev 1.5 and stable 1.4

[bplus]

I started checking constants from initial Qwerkey file alert (Pi in the Sky) and ran into a red line pretty quickey, see attached.

  [ You are not allowed to view this attachment ]  

[FellippeHeitor]

It doesn't have to do with CONST, but with CamelCase. Making keywords all caps makes the error go away. Thanks for reporting.

[bplus]

Error go away, another way, see attached
  [ You are not allowed to view this attachment ]  

[FellippeHeitor]

Interesting.

[FellippeHeitor]

Please get the latest dev build, generated just now from git 64d149b. I believe I fixed the const+camelcase issue.

Also, check out the new auto-complete feature...

[bplus]

@FellippeHeitor I found another weird one

SunSize%% is coming up -12  ???

Code: QB64: [Select]

1. Const PiSizeLess1% = 499, PiDisp% = 100, SunSize%% = 500, AmblinHalf%% = 50
2. Print PiSizeLess1%; PiDisp%; SunSize%%; AmblinHalf%% '>>>  SunSize%% -12 ??? wierd!
3.  
4.  

I will check your next version. Oh man that's (auto-complete) going to be something!

[FellippeHeitor]

You are forcing the constant to have the type _BYTE (-128 to 127). Are you following my logic?

[SMcNeill]

%% is a byte, with values from -128 to 127.  Your value of 500 is overflowing and only  returning the one byte out of your two-byte value.

[bplus]

Yeah got it, did not recognize the suffix for some reason I was thinking LONG like it is double an Integer ;-))

Anyway, I wonder if Qwerkey knew what he was doing there.

[RhoSigma]

Not directly CONST related, but nevertheless it seems to match into this topic.
Probably another camel case issue? At least it worked in earlier (pre-camel) versions.

Positive/negative DECIMAL numbers with explicit type suffix added are not highlighted anymore (eg. 3.14#, 25&, -4096&& etc.)

As said it affects decimal numbers only, &B/&H/&O prefixed numbers such as &HFF&&, &B1111& are working ok.

BTW - It doesn't matter if camel case is on/off, it's not highlighted in either mode.

[FellippeHeitor]

Will check. Do you remember when it used to work?

[RhoSigma]

At least it worked until stable v1.4, but not in the current dev build. Will look in the repo to find the last git before camel case was injected and test, hold on for 5 mins.

UPDATE:
So it is already broken in git b28a929 from Jan/30, which was right before the introduction of camel case, so obviously that's not the cause of it, going back further...

[FellippeHeitor]

Just confirmed it worked ok in 1.4. The highlighter was tweaked in 1.5 because it was not working for scientific notation numbers - I apparently missed that usage you're showcasing here too (cause I never use it). Thanks for letting me know.

[FellippeHeitor]

Likely the changes introduced in https://github.com/QB64Team/qb64/commit/8f19321c06870b83be1b7d6a1d894ddc5a662dac - thanks for helping look for it!

[FellippeHeitor]

@RhoSigma, if you can, please grab the dev build I just pushed now into the repo (from git 711e686), and the issue should be fixed.