Incorrect `whitespace_011` for real values with negative exponent

[ru551n]

Environment
VSG version 3.27.0
Windows 11

Describe the bug
Incorrect failure when calling functions with real values which have negative exponent.

To Reproduce

my_function(1.0e-3)

Will incorrectly yield a whitespace_011 (space around math operators) stating that space is required around the - sign.

Expected behavior
Functions should be able to take real values with negative exponent. Having a space around the operator is a syntactic error.

[jeremiah-c-leary]

Afternoon @ru551n ,

I checked out version 3.27.0 and ran the following test case:

architecture rtl of fifo is

begin

  a <= my_function(1.0e-3);

end architecture rtl;

...but I do not get any errors reported:

$ bin/vsg -f rule_011_test_input.vhd
================================================================================
File:  rule_011_test_input.vhd
================================================================================
Phase 7 of 7... Reporting
Total Rules Checked: 769
Total Violations:    0
  Error   :     0
  Warning :     0

Looking at what the rule operates on and how the minus sign is classified, I would not expect the rule whitespace_011 to apply.

Could you provide a minimal code sample, similar to what I showed above, that exhibits the problem?

Thanks,

--Jeremy

[jeremiah-c-leary]

Morning @ru551n ,

Just wanted to ping you on this issue to see if we could keep it moving forward.

Thanks,

--Jeremy

[jeremiah-c-leary]

Afternoon @ru551n ,

I pushed an update to the issue-1433 branch. When you get a chance could you check it on your end and let me know if it fixes the issue for you?

Thanks,

--Jeremy

[domWalters]

Hi @jeremiah-c-leary,

I've just encountered this issue as well with defining a real in a generic map also triggering whitespace_011.

I can't see a branch called issue-1433?

[jeremiah-c-leary]

Morning @domWalters,

It looks like the issue-1433 branch was merged to master on April 6th. I just pushed the new release 3.32.0 which contains the fix. Could you update to the latest version and let me know if the problem still exists or has been fixed?

Thanks,

--Jeremy

[domWalters]

@jeremiah-c-leary, apologies for the slow reply.

I tried replicating my issue with a real generic constant and have been unable to on 3.33.0.

[jeremiah-c-leary]

Awesome, I will close this issue.

--Jeremy