Support other types of integer literals, and underscores

[Chuck]

"0o" for octal.
"0b" for binary.
Support underscore separators in integer literals regardless of their base. This is already supported in the "standard" integer literals like "1_000_000".

[hopscc]

see Discussion AnyOne for a Hex and closed Ticket#28

[hopscc]

patch for binary and octal literals, _ separators in such lits.
Changes to hex lit support. Tests and IntRelNotes updates.

Provides both signed and unsigned support.
Syntax changed from orig in hexLits
literal must specify both size and sign ( _?(u|i)(8|16|32|64)?
previously could specify just size (_?(8|16|32|64)

[Chuck]

Patch application failed. Maybe do a "svn up" and try again? Or apply the fix you discovered previously?

>patch -p0 -i binOctLit.patch
patching file Source/CobraTokenizer.cobra
Hunk #2 succeeded at 476 (offset -103 lines).
Hunk #3 FAILED at 489.
1 out of 3 hunks FAILED -- saving rejects to file Source/CobraTokenizer.cobra.rej
patching file Tests/100-basics/922-bin-lit.cobra
patching file Tests/100-basics/920-hex-lit.cobra
patching file Tests/100-basics/924-oct-lit.cobra
patching file Developer/IntermediateReleaseNotes.text

I looked at the "reject" file, but didn't get a clue as to the problem. Also, there was too much in there to apply by hand.

I'm on Windows, fyi.

[hopscc]

It was generated against an up to date tree last night and pretested fine against that. (also on WIndows) - (I 've been the applying the workround and pretesting before posting the patch)

Strange: I just downloaded it and ran it against a clean tree here and it patched fine.

  > svn st -u
  ?                   Source\mkcobc
  ?                   Source\mktests
  ?                   Source\CobraInfo.cs  
  ?                   Source\Snapshot\CobraInfo.cs
  ?                   binOctLit.patch
  Status against revision:   1551

  > patch -p0 -i binOctLit.patch
  patching file Source/CobraTokenizer.cobra
  patching file Tests/100-basics/922-bin-lit.cobra
  patching file Tests/100-basics/920-hex-lit.cobra
  patching file Tests/100-basics/924-oct-lit.cobra
  patching file Developer/IntermediateReleaseNotes.text
  > svn st
  ?      binOctLit.patch
  ?      Source\mkcobc
  ?      Source\mktests
  ?      Source\CobraInfo.cs
  ?      Source\Snapshot\CobraInfo.cs
  M      Source\CobraTokenizer.cobra
  ?      Tests\100-basics\922-bin-lit.cobra
  ?      Tests\100-basics\924-oct-lit.cobra
  M      Tests\100-basics\920-hex-lit.cobra
  M      Developer\IntermediateReleaseNotes.text
  >

What happened to hunk#1
Thats an awfully big offset for hunk #2 against a clean tree (103 lines back
-thats starting that hunk at about line 470 ??)
what happened to the previous 100 lines in CobraTokenizer???

I can give you a verbatim cut of the failing hunk as separate text if you like - its pretty much an insertion of code anyway

[hopscc]

heres hunk#2 anyway.

[hopscc]

OOps - while named hunk2 it actually contains hunk3 - the one that failed...