#1115: show results of expressions in HLLCompiler based repls (again)
----------------------+-----------------------------------------------------
Reporter: riffraff | Owner: pmichaud
Type: feature | Status: new
Priority: normal | Milestone:
Component: PCT | Version: trunk
Severity: medium | Keywords: repl
Lang: | Patch: new
Platform: all |
----------------------+-----------------------------------------------------
Comment(by riffraff):
Replying to [comment:1 jkeenan]:
> > All parrot and rakudo tests seem to pass, which means that probably
> > there are no tests for this functionality at all.
> >
>
> If this is the case, and if this patch touches several of the Parrot
tools as you indicate, then the first step would be to write the tests
needed. I would not recommend adding more functionality to an untested
area.
sorry I must have failed to express myself: it does not touch much, if you
look at the patch it only does skin-deep changes, about ten lines.
And it does them to an area which basically nobody tests.. I presume
because it's difficult to test with the current infrastructure, and
because changes are close enough to the surface of the software that they
seldom cause problems.
But I understand why untested code should not go in, I just reposted the
one year old patch and have no time to improve it now, I'm sorry.
Frankly, though, I believe going from this
{{{
> mecbuc:~/Dev/rakudo rff$ ./perl6
> 1
> 1+12
> 1+3;
> print 1;
1> say 1
1
}}}
to
{{{
mecbuc:~/Dev/rakudo rff$ ./perl6
>> 1
=> 1
>> 1+12
=> 13
>> my $v = [1,2,45]
=> 1 2 45
>> print 'hello'
hello=> 1
>> say 'kewl'
kewl
=> 1
>>
}}}
should be pretty close to the top of the wanted features for any
interpreter :)
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1115#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
