Re: [TCLCORE] RFC: Octal options

[Jan N. <nij...@us...>]

Let's call Andreas' variant Option 2a
  Option 2a: Noisy incompatible change.  Ambiguous leading zero -> error.
        "01"  : Legal integer value 1
        "08"  : Legal integer value 8 (not really Ambiguous because it
can't be octal)
        "010" : Error
        "017" : Error
        "018" : Error (not really Ambiguous either, but it is not
useful to accept
                            it either. Why would we disallow 017 and
allow 018.....)
  This option has the advantage that all 2-digit numbers are interpreted as
  valid decimal integers already.

Then my first choice would be Option 2, but I could very well live with
Option 2a as well. It is true that Option 2 doesn't go far enough to
be really usefull: It merely starts to annoy users who still dare to use
this octal notation. But I see it as an upgrade path, leading
to Option 4 - eventually - in Tcl 9.0.

Option 2a fixes Joe's complaint:
> Option 2 doesn't go far enough to help much: scripts that
> use octal on purpose would break, but scripts that use
> octal by accident would still appear to work 10 months out
> of the year and only break in August and September.

Regards,
        Jan Nijtmans