| Author |
 Topic  |
|
|
.oisyn
Tomato Guru
162 Posts |
 Posted - Oct 25 2022 : 6:39:58 PM
|
In C++20's modules, you can use the dot in a module's name. It has no hierarchical significance whatsoever, it's just an allowed character. However, VA seems to break up these module names and make the individual parts accessible as symbols.
For instance, when you have a module called "foo.std" and you import it like so: import foo.std;
VA subsequently colors all occurences of "std" using the color for variables, rather than the color for namespaces like it would normally do.
I would expect VA to parse module names as-is, but I'd be perfectly fine with an alternative solution where module names are skipped over altogether and not clutter the table of symbols at all, as they're essentially not even C++ symbols. |
Edited by - .oisyn on Oct 25 2022 7:22:32 PM |
|
|
feline
Whole Tomato Software
United Kingdom
19014 Posts |
Posted - Nov 15 2022 : 11:59:53 AM
|
Apologies for the slow reply, I am seeing some colouring problems with a dot in a module name, but not the follow on problems with "std" that you are describing. In the file where I am using my module with a dot in the name I have the following result:
this is VS2022, with VA 2463, and IDE intellisense disabled, so the pink underlining is coming from VA, which just confirms our parser isn't expecting a dot in the module name:
We are still working on C++20 module support, so I have added this to our modules case, since it is good to be aware of it:
case=95226 |
zen is the art of being at one with the two'ness |
 |
|
| |
Topic |
|
|
|
dot in module names throws off VA parser
