Divider bits in the binary values

[4RESTER]

In FASM is a separator for the binary values, such divider is a symbol Chr($27), and it works in the InlineAsm version, for example:

Code: Select all

! DD 1111'0000'10100101'00000000'11'1111'11b
! MOV  EAX,1111'0000'10100101'00000000'11'1111'11b

(in other assemblers as a separator binary values can be used the character "_")

This is very useful for visual interpretation of binary values.

Can You add a bits separator of the binary values for the PureBasic?

To be used in expressions such as:

Code: Select all

A = %111_0_0101_1_000_1111
Data.W     %111_0_0101_1_000_1111

[blueznl]

Oh yeah, this one I like! Also for hex please... $AF_CC_DE_FF and so on...

[4RESTER]

Oh yeah, this one I like! Also for hex please... $AF_CC_DE_FF and so on...

Unfortunately, as I thought, the authors of PureBasic, not in a hurry to really useful innovation.
Very sorry.
For example - the author of FASM does it literally within an hour.

At the moment I refused to use PureBasic. Use a clean FASM.

[remi_meier]

Oh yeah, this one I like! Also for hex please... $AF_CC_DE_FF and so on...

Unfortunately, as I thought, the authors of PureBasic, not in a hurry to really useful innovation.
Very sorry.
For example - the author of FASM does it literally within an hour.

At the moment I refused to use PureBasic. Use a clean FASM.

Seems like FASM doesn't do serious regression testing.
@PB-Team: Are you sure you still want to depend on
such untested software?

On a more serious note:
The PB-Team has a release cycle where you should
be able to rely on the stability of a released version.
That includes regression tests after adding new features
like this. Maybe you want to apply for the Alpha-testing
team (I'm not one of them) and then you'll see faster
feature inclusion but also delay and canceling.
Every serious developer knows that even the tiniest
of changes can result in hard to detect show-stopper
bugs.

greetz
remi