Re: [PATCH 1/3] deprecate . immediately after hex/oct/bin literal

I wrote:
>Expressions such as "0x1.8" (concatenation of two numbers, the first
>being a hex/oct/bin literal) will now warn.

This patch is redundant with a different one that got applied to blead
earlier today.  I'm sending it for two reasons.  Firstly because (as
discussed on IRC) I'm also sending two more patches regarding deprecating
parts of numeric syntax, and those patches were originally built on top
of this one, so this provides context.  (I can rebase the patches if
that turns out to be more helpful, of course.)

Secondly because some parts of this patch may be worth merging with
what's just gone on blead.  I think I have a better warning message,
in so far as it actually uses the word "deprecated".  And the tests here
are more systematic.  Someone else should go through the two patches to
pick the best of each.

-zefram

• [PATCH 1/3] deprecate . immediately after hex/oct/bin literal by Zefram
• [PATCH 3/3] deprecate exponent with no digits by Zefram
• Re: [PATCH 1/3] deprecate . immediately after hex/oct/bin literal by Jesse Vincent
• Re: [PATCH 1/3] deprecate . immediately after hex/oct/bin literal by Zefram
• [PATCH for tests] Re: [PATCH 1/3] deprecate . immediately after hex/oct/bin literal by Dominic Dunlop
• Re: [PATCH for tests] Re: [PATCH 1/3] deprecate . immediatelyafter hex/oct/bin literal by Zefram
• Re: [PATCH 1/3] deprecate . immediately after hex/oct/bin literal by James Mastros
• Re: [PATCH 1/3] deprecate . immediately after hex/oct/bin literal by Jesse Vincent
• Re: [PATCH 1/3] deprecate . immediately after hex/oct/bin literal by Andy Dougherty
• Re: [PATCH 1/3] deprecate . immediately after hex/oct/bin literal by Zefram