Improve ASSERT Macro to Handle Operator Precedence More Intuitively

[ping-ee]

Description

The current implementation of the ASSERT macro requires extra parentheses to handle operator precedence correctly, such as:

`ASSERT((a===b));  // Correct

Without these parentheses, expressions may lead to incorrect logic due to operator precedence rules.

For example, a developer might mistakenly write:

`ASSERT(a === b);  // Wrong

This could be misinterpreted by the compiler as:

if (!a === b)  // Wrong behavior

Instead of the intended:

if (!(a === b))  // Correct logic when using parentheses.

Proposed Solution:

svut/svut/svut_h.sv

Line 159 in d2b4d62

if (!exp) begin \

Use a pair of parentheses to wrap exp such as:

if (!(exp)) begin

Benefits:

1. Prevents potential logical errors due to misunderstood operator precedence.
2. Improves developer productivity by making the ASSERT macro behavior more intuitive.
3. Reduces debugging time caused by precedence-related bugs.

Thanks for your work on this framework, it definitely helps me a lot.

Best Regards

[dpretet]

Hello,

That looks to be definitely a good improvement 😄 It's true I faced sometimes this problem, and adding these extra parentheses makes the code weird to read. I have to do a release with a fix for issue #28, a pull request for that proposal is welcome 🤗

Thanks for your feedback and using this flow !

Best,
Damien

[ping-ee]

Sure, I will submit a pull request for this issue in a few days.
Thanks for your reply.

[dpretet]

Thank you for the contribution!