| Author |
 Topic  |
|
|
Zeblote
Tomato Guru
183 Posts |
 Posted - May 15 2018 : 2:01:00 PM
|
"BrickBox" should be green, since it is not a method. I don't have any methods called "BrickBox". |
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - May 15 2018 : 3:15:27 PM
|
Thank you for the clear screen shot. This is currently a known problem with our colouring code. Just looking at the code in the screen shot, it's not instantly obvious that "BrickBox" is a variable and not the name of a function, since the syntax looks a lot like a function declaration. We want our colouring code to run very quickly, so it can keep up with you working, but that does leave us prone to some problems.
case=60805 |
zen is the art of being at one with the two'ness |
 |
|
|
Zeblote
Tomato Guru
183 Posts |
Posted - May 15 2018 : 3:28:55 PM
|
quote:
Originally posted by feline
Thank you for the clear screen shot. This is currently a known problem with our colouring code. Just looking at the code in the screen shot, it's not instantly obvious that "BrickBox" is a variable and not the name of a function, since the syntax looks a lot like a function declaration. We want our colouring code to run very quickly, so it can keep up with you working, but that does leave us prone to some problems.
case=60805
Is it possible to detect that it is currently inside a function definition and thus there can be no other ones? |
|
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - May 16 2018 : 10:26:10 AM
|
To a degree we do try and do this. The bug is actually a bit more specific than just looking like a function signature. If you are passing literal integer values to the constructor then VA will colour the code correctly, but the bug shows up when passing parameters to the constructor.
Trying to make perfect sense of C++ without getting to compile it is "interesting" :) |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
Wrong color for local variable
