of course, the clear choice to follow when using hexidecimal literals is the C way:
example: 0x1F
instead of the VB way: &h1F
the C way looks cleaner, and is easier to remember. Every time I go to put in a hexidicimal in vb, I have to go look it up again, but the first time I saw the C way, it was easy to remember, and I havent forgotten since.
We need a similar notation for octal and binary numbers. I think this workes nicely:
0b101000011011
0o723162
Also, I think we should steal a concept from eiffel. eiffel allows for underscores within numeric literals to group digits, making it easier to read: like so:
In eiffel, 1000 could be written 1_000
obviously, we cant use a comma to sepearate the values, or they would be considered 2 different values (parameters to functions are seperated by commas, that would be ambiguous.)
of course, using and underscore to group digits would be nice for hex, bin and oct numbers not just "normal" decimal values.
of course, the clear choice to follow when using hexidecimal literals is the C way:
example: 0x1F
instead of the VB way: &h1F
the C way looks cleaner, and is easier to remember. Every time I go to put in a hexidicimal in vb, I have to go look it up again, but the first time I saw the C way, it was easy to remember, and I havent forgotten since.
We need a similar notation for octal and binary numbers. I think this workes nicely:
0b101000011011
0o723162
Also, I think we should steal a concept from eiffel. eiffel allows for underscores within numeric literals to group digits, making it easier to read: like so:
In eiffel, 1000 could be written 1_000
obviously, we cant use a comma to sepearate the values, or they would be considered 2 different values (parameters to functions are seperated by commas, that would be ambiguous.)
of course, using and underscore to group digits would be nice for hex, bin and oct numbers not just "normal" decimal values.
Hexidecimal: 0xAF19_56F1
0x4E77EC8F_51D8_386C_85FE_7DC931B7A8E7
Binary: 0b0110_1010_1000_1111
Octal: 0o351_270
Decimal 2_147_483_647