parser or compiler?
> If they aren't, maybe a) the docs should be more explicit, and b), the
> diagnostics should say so, immediately?
>
> perl6 -v
> This is Rakudo Star version 2019.03.1 built on MoarVM version 2019.03
>
eave it as "an exercise for the reader".
If unpaired boundary characters like these are legal, presumably
there's a problem with the parser or compiler?
If they aren't, maybe a) the docs should be more explicit, and b), the
diagnostics should say so, immediately?
perl6
Thank you!
Thank you!
dition IMHO the final report should also say "1 todo"
>
> Our repo is https://github.com/Bailador/Bailador
>
> I've posted this to the TAP::Harness project but Leon Timmermans
> directed me to Test.pm6
> https://github.com/perl6/tap-harness6/issues/17
>
> &qu
dition IMHO the final report should also say "1 todo"
>
> Our repo is https://github.com/Bailador/Bailador
>
> I've posted this to the TAP::Harness project but Leon Timmermans
> directed me to Test.pm6
> https://github.com/perl6/tap-harness6/issues/17
>
> &qu
On Wed, 19 Jul 2017 16:46:20 -0700, c...@zoffix.com wrote:
> Gonna take care of this in the next 26hr
I lied. Need more time.
The fix I planned to do solved the issue, but now it's reporting the subtest as
an unexpectedly-passing TODO heh :P
Gonna think about it for another day or two, giv
On Wed, 19 Jul 2017 16:46:20 -0700, c...@zoffix.com wrote:
> Gonna take care of this in the next 26hr
I lied. Need more time.
The fix I planned to do solved the issue, but now it's reporting the subtest as
an unexpectedly-passing TODO heh :P
Gonna think about it for another day or two, giv
dition IMHO the final report should also say "1 todo"
>
> Our repo is https://github.com/Bailador/Bailador
>
> I've posted this to the TAP::Harness project but Leon Timmermans
> directed me to Test.pm6
> https://github.com/perl6/tap-harness6/issues/17
>
> &qu
dition IMHO the final report should also say "1 todo"
>
> Our repo is https://github.com/Bailador/Bailador
>
> I've posted this to the TAP::Harness project but Leon Timmermans
> directed me to Test.pm6
> https://github.com/perl6/tap-harness6/issues/17
>
> &qu
e mode.
In addition IMHO the final report should also say "1 todo"
Our repo is https://github.com/Bailador/Bailador
I've posted this to the TAP::Harness project but Leon Timmermans
directed me to Test.pm6
https://github.com/perl6/tap-harness6/issues/17
"That output has nothi
This might be a useful point of reference for thinking about diagnostics and
what's important to the developer working with Perl 6 in the future:
http://clang.llvm.org/diagnostics.html
On Mon Jun 30 07:53:20 2008, coke wrote:
> Find a perlcritic-sane way to silence this warning for codetest:
>
> Policy "Perl::Critic::Policy::Bangs::ProhibitFlagComments" is not
installed.
>
Fixed in r28867.
--
Will "Coke" Coleda
# New Ticket Created by Will Coleda
# Please include the string: [perl #56470]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56470 >
Find a perlcritic-sane way to silence this warning for codetest:
Policy "Perl::Critic::P
# New Ticket Created by Will Coleda
# Please include the string: [perl #39831]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39831 >
$ ../../parrot ../../compilers/tge/tgc.pir --output=src/grammar/
post2pir.pir src/gramma
MY BUSINESS IS DONE!
Test diagnostics now look like this:
not ok 21 - foo is bar?
# Failed test 'foo is bar?'
# in t/foo.t at line 40.
# got: 'foo'
# expected: 'bar'
If there's no description it looks like this:
not ok 21
#
On Thu, Apr 28, 2005 at 10:08:00PM -0400, James E Keenan wrote:
> Fergal Daly wrote:
> >Where is TEST_VERBOSE documented? I see HARNESS_VERBOSE in
> >
> >http://search.cpan.org/~petdance/Test-Harness-2.48/lib/Test/Harness.pm
>
> http://search.cpan.org/grep?release=Test-Harness-2.48&string=TEST_VER
Fergal Daly wrote:
Where is TEST_VERBOSE documented? I see HARNESS_VERBOSE in
http://search.cpan.org/~petdance/Test-Harness-2.48/lib/Test/Harness.pm
F
http://search.cpan.org/grep?release=Test-Harness-2.48&string=TEST_VERBOSE&n=1
HTH
jimk
On Thu, Apr 28, 2005 at 02:44:30PM +0100, Adrian Howard wrote:
>
> On 28 Apr 2005, at 14:23, Paul Johnson wrote:
>
> >Using Test::More, I would like to send some diagnostics to be seen only
> >when the harness is running in verbose mode.
> [snip]
>
> diag
On Thu, Apr 28, 2005 at 02:44:30PM +0100, Adrian Howard wrote:
> On 28 Apr 2005, at 14:23, Paul Johnson wrote:
>
> >Using Test::More, I would like to send some diagnostics to be seen only
> >when the harness is running in verbose mode.
> [snip]
>
> diag "s
uld like to send some diagnostics to be seen only
> > when the harness is running in verbose mode.
> [snip]
>
> diag "some verbose diagnostics" if $ENV{TEST_VERBOSE};
>
> ?
>
> Adrian
>
>
On 28 Apr 2005, at 14:23, Paul Johnson wrote:
Using Test::More, I would like to send some diagnostics to be seen only
when the harness is running in verbose mode.
[snip]
diag "some verbose diagnostics" if $ENV{TEST_VERBOSE};
?
Adrian
Using Test::More, I would like to send some diagnostics to be seen only
when the harness is running in verbose mode.
There doesn't seem to be a way of doing this. The best I could come up
with is:
sub vdiag { pass("@_") }
but this has little to recommend it.
Thoughts?
-
23 matches
Mail list logo