From glitchmr@myopera.com

If I write something like `say 09`, Rakudo warns about octal numbers
twice. Also, "octal" numbers don't work in REPL.

From @masak

<masak> GlitchMr​: the phrase "don't work" is generally taboo in bug
reports.
<GlitchMr> sorry
<masak> GlitchMr​: you should be talking about what you did, what you
observe, and what you expected.
<GlitchMr> Null PMC access in get_string()
<masak> right. that should be in there.
<masak> GlitchMr​: the goal is to have enough information that the thing
can be checked again later.
* masak adds this to the ticket

The RT System itself - Status changed from 'new' to 'open'

From glitchmr@myopera.com

By REPL not working, I mean that every time octal number appears, "Null
PMC access in get_string()" appears. Sorry for not mentioning that
initially.

From @skids

Fresher test results​: no duplicate warnings, NULL pointers in REPL
under parrot and jvm but not moar. Probably LTA to be telling the
user to use '0o8' or '0o9'.

NOTE​: my perl6-p is Star.2014.12 and my perl6-j/m are built from star-daily
Cologne-256-gd78c678.

$ perl6-p -e 'say 09'
Potential difficulties​:
  Leading 0 does not indicate octal in Perl 6; please use 0o9 if you mean that
  at -e​:1
  ------> say 09⏏<EOL>
9
$ perl6-m -e 'say 09'
Potential difficulties​:
  Leading 0 does not indicate octal in Perl 6; please use 0o9 if you mean that
  at -e​:1
  ------> say 09⏏<EOL>
9
$ perl6-j -e 'say 09'
Potential difficulties​:
  Leading 0 does not indicate octal in Perl 6; please use 0o9 if you mean that
  at -e​:1
  ------> say 09⏏<EOL>
9
$ perl6-p

say 09
Null PMC access in get_string()
say 09;
Null PMC access in get_string()
say 8
8
exit
$ perl6-m
say 09
Potential difficulties​:
  Leading 0 does not indicate octal in Perl 6; please use 0o9 if you mean that
  at <unknown file>​:1
  ------> say 09⏏<EOL>
9
say 9
9
exit
$ perl6-j
say 09
java.lang.NullPointerException

From @coke

On Sun Feb 01 12​:33​:27 2015, bri@​abrij.org wrote​:

Fresher test results​: no duplicate warnings, NULL pointers in REPL
under parrot and jvm but not moar. Probably LTA to be telling the
user to use '0o8' or '0o9'.

NOTE​: my perl6-p is Star.2014.12 and my perl6-j/m are built from star-
daily
Cologne-256-gd78c678.

$ perl6-p -e 'say 09'
Potential difficulties​:
Leading 0 does not indicate octal in Perl 6; please use 0o9 if you
mean that
at -e​:1
------> say 09⏏<EOL>
9
$ perl6-m -e 'say 09'
Potential difficulties​:
Leading 0 does not indicate octal in Perl 6; please use 0o9 if you
mean that
at -e​:1
------> say 09⏏<EOL>
9
$ perl6-j -e 'say 09'
Potential difficulties​:
Leading 0 does not indicate octal in Perl 6; please use 0o9 if you
mean that
at -e​:1
------> say 09⏏<EOL>
9
$ perl6-p

say 09
Null PMC access in get_string()
say 09;
Null PMC access in get_string()
say 8
8
exit
$ perl6-m
say 09
Potential difficulties​:
Leading 0 does not indicate octal in Perl 6; please use 0o9 if you
mean that
at <unknown file>​:1
------> say 09⏏<EOL>
9
say 9
9
exit
$ perl6-j
say 09
java.lang.NullPointerException

This works as expected in the REPL and out. Can be closed with tests.

--
Will "Coke" Coleda

From @zoffixznet

LTA warning fixed in rakudo/rakudo@6d0cc07

Warning tests added in Raku/roast@e669003e22
REPL tests added in Raku/roast@7dce301ae7

@zoffixznet - Status changed from 'open' to 'resolved'