From losch@uni-bonn.de

In the rakudo-moar shell
my int32 $t=0;
$t.say;
The second line will produce
«Unhandled lexical type in lexprimspec for '$t'»
after any next command, you have to terminate the perl-shell.

From @usev6

Some additions to this ticket​: There is no error when both commands are on the same line​:

$ echo 'my int64 $t=0; $t.say' | perl6-m
0

The error is still reproducable when the commands are on separate lines (there is a newline in the shell command)​:

$ echo 'my int32 $t=0;
$t.say' | perl6-m
0
Unhandled lexical type in lexprimspec for '$t'

But this does not happen with type 'int' or 'int64'​:

$ echo 'my int $t=0;
$t.say' | perl6-m
0
0

$ echo 'my int64 $t=0;
$t.say' | perl6-m
0
0

The above output is from a 64bit Linux box​:

$ $ uname -a
Linux cus 3.2.0-4-amd64 #​1 SMP Debian 3.2.65-1+deb7u1 x86_64 GNU/Linux

@usev6 - Status changed from 'new' to 'open'

From @usev6

After reading http://irclog.perlgeek.de/perl6/2015-02-25#i_10176273 I tried again and found that there also is a problem with types 'int' and 'int64'. It shows up when setting $t to something else then 0​:

$ echo 'my i32 $t=4;
$t.say' | perl6-m
4
Unhandled lexical type in lexprimspec for '$t'

$ echo 'my int $t=4;
$t.say' | perl6-m
4
0

$ echo 'my int64 $t=4;
$t.say' | perl6-m
4
0

Anyway, looks like this will be fixed soonish (see the link above).

From @usev6

The case with 'int32' does not work yet, but the rest looks good. (And I groked how to test multiline input to the REPL).

$ perl6-m --version
This is perl6 version 2015.02-151-g669f482 built on MoarVM version 2015.02-17-g86d0c68

$ (echo 'my int $t=4'; echo '$t') | perl6-m
4
4

$ (echo 'my int64 $t=4'; echo '$t') | perl6-m
4
4

$ (echo 'my int32 $t=4'; echo '$t') | perl6-m
4
Unhandled lexical type in lexprimspec for '$t'

From @MARTIMM

Hi,

Found a strange bug in REPL;

my int8 $i = 0x78;
120
my int8 $j = 0x78;
Unhandled lexical type in lexprimspec for '$i'

The same for error generated with types int16, int32 and int64 but not
for int.

There are no errors when this command was given;

perl6 -e 'my int8 $i=0x78; my int8 $j=0x78; say "$i, $j";'
120, 120

This is Rakudo version 2016.02-136-g412d9a4 built on MoarVM version
2016.02-25-gada3752
implementing Perl 6.c.

greetings,
Marcel

From @zoffixznet

Still present in Rakudo version 2016.07.1-12-g58dc8c6 built on MoarVM version 2016.07.

The code after `my int8 $a = 42;` doesn't matter. Even a bare ';' produces the error and 'exit' is broken altogether.

♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥
🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁

TODO-fudged tests added in Raku/roast@c0504f94d6

🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁🏁
♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥

Cheers,
ZZ

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

From @zoffixznet

This issue appears to no longer be there.

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

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

From @zoffixznet

The issue is actually still there and was merely hidden by another bug.

From @usev6

Just a note​: This seems to be a specific problem with Moar​:

$ ./perl6-j
[...]

my int8 $i = 0x78;
120
my int8 $j = 0x78;
120

I'm going to tag this ticket with [MoarVM]. Or should the ticket be moved to the Github repo for MoarVM?

From @zoffixznet

On Sun, 28 Aug 2016 09​:40​:51 -0700, bartolin@​gmx.de wrote​:

Just a note​: This seems to be a specific problem with Moar​:

$ ./perl6-j
[...]

my int8 $i = 0x78;
120
my int8 $j = 0x78;
120

I'm going to tag this ticket with [MoarVM]. Or should the ticket be
moved to the Github repo for MoarVM?

Closing as the ticket now moved to GitHub​: rakudo/rakudo#2284

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