thousands separator in constants

[440bx]

Hello,

I'm probably getting some programming languages mixed but I was under the impression that some FPC version started supporting "_" as a thousand separator in numeric constants, e.g,

Code: Pascal  [Select][+][-]

1. const
2.   SOME_CONSTANT = 100_000;

but that rewarded me with "Error: Syntax error, ";" expected but "identifier _000" found"

The question is: does FPC support the use of "_" as a thousand separator and if it does, what setting must be set to enable its use ?

Thank you for your help.

PS: if FPC doesn't support "_" as a thousands separator, it would be nice if it did

[Thaddy]

It is available in fpc trunk/main, but only in trunk/main afaik.
It is not available in fpc 3.2.x
https://wiki.freepascal.org/FPC_New_Features_Trunk#Support_for_Digit_Separator

[cdbc]

Hi
I just tried, it does not compile in:

Code: [Select]

Free Pascal Compiler version 3.3.1-15019-g664f8fc2ba-dirty [2024/01/28] for x86_64
Copyright (c) 1993-2024 by Florian Klaempfl and others
Target OS: Linux for x86-64
Regards Benny

[Thaddy]

As per my link:
It is enabled by default in the delphi modes.

In other modes it needs

Code: Pascal  [Select][+][-]

1. {$modeswitch underscoreisseparator }

But still :a recent 3.3.1 main is necessary.

[440bx]

It is available in fpc trunk/main, but only in trunk/main afaik.
It is not available in fpc 3.2.x
https://wiki.freepascal.org/FPC_New_Features_Trunk#Support_for_Digit_Separator

and unfortunately it seems to require {$mode Delphi}, it doesn't work in non-Delphi mode.

I wonder why the devs limited it to Delphi mode only... seems like it would be a good idea to make it available in all modes (there doesn't seem to be a good reason to limit it to a specific mode.)

Thank you for your help and thank you cdbc too.

[Thaddy]

unfortunately it seems to require {$mode Delphi}, it doesn't work in non-Delphi mode.

No, it requires a mode switch in other modes.

Code: Pascal  [Select][+][-]

1. {$modeswitch underscoreisseparator }

Personally I hope it stays that way, but I guess that will be not the case in the future.

[440bx]

I'd love to see that modeswitch back ported to v3.2.2

[PascalDragon]

I'd love to see that modeswitch back ported to v3.2.2

3.2.2 is a released version, it will never change.

So the only possibility is 3.2.3 which will become 3.2.4, but in general we don't backport compiler features to the fixes branch.

[440bx]

3.2.2 is a released version, it will never change.

I meant one of its "offsprings" but you're right, that wording expressed an impossibility (it wouldn't really be version 3.2.2 anymore.)

So the only possibility is 3.2.3 which will become 3.2.4, but in general we don't backport compiler features to the fixes branch.

That's understandable since that isn't a fix. It would be nice though.