Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
 Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Feature Requests
 if likelyMacro/constexpr destroy parse		  New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

superzmy
Senior Member

China
26 Posts
Posted - Dec 19 2024 :  10:07:48 AM  Show Profile  Reply with Quote
void A()
{
if constexpr (1)
{
}
int x;
}
------
void A()
{
if MYMACRO(1)
{
}
int x;
}
cause VA Outline tree level broken

superzmy
Senior Member

China
26 Posts
Posted - Dec 19 2024 :  10:25:17 AM  Show Profile  Reply with Quote
and prevent symbol reference of CALL about
if MYMACRO(CALL())
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
19054 Posts
Posted - Dec 19 2024 :  3:37:03 PM  Show Profile  Reply with Quote
Thank you for the clear examples. It turns out the constexpr version of the bug is a known problem, but I didn't know this could happen with a macro after an if statement. That is quite odd, but very easy to reproduce once you know what the trigger is:

case=144299
zen is the art of being at one with the two'ness
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000