Improve library

[jubianchi]

I recently opened 3 linked PRs and they all need to be discussed correctly to be integrated altogether.

Let's sum-up:

• Constants #38: adds new constants (original PR was Added constants to Arithmetic #20)
• Allow constants names to start with digits #39: allows constants/ids names to start with digits
• Add support for hexadecimal, octal and binary values #40: adds support for hex/oct/bin notations

The #38 and #40 are ready, event though the #38 is kind of blocked by #39. What I think we should do:

• Close the Allow constants names to start with digits #39 thus disallowing constants/ids names to start with digits
• Edit the Constants #38 to remove constants starting with digit (and replace those with their plain names, e.g 2_ => TWO_)
• Edit Add support for hexadecimal, octal and binary values #40 to use standard/generic notation for hex (0x...), octal (0...) and binary (0b...)
• Keep standard decimal notation, e.g no prefix for them (1337 would just be 1337)
• Merge Constants #38
• Merge Add support for hexadecimal, octal and binary values #40

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[Hywan]

Why should we disallow constant to start by a digit? I don't see why is it an issue here.

[jubianchi]

@Hywan because if we don't, we can't support generic notations for hex/bin/oct...

Or we could be we'll have to enforce conventions like "A variables name can start with a digit but can't start with 0x or 0b". The same applies to constants: they can start with digits but not 0X which will be recognized as a hex notation.

[Hywan]

Good. So 👍 for closing #39, 👍 to restore previous constant names, and 👍 for #40 (but its testing suite must be updated and robust).

[jubianchi]

@Hywan will do ;) Thanks!

[Hywan]

Some news?

[Hywan]

ping?