svn switch --relocate svn.openfoundry.org/pugs svn.pugscode.org/pugs/ | run.pugscode.org | spec.pugscode.org | paste: sial.org/pbot/perl6 | pugs.blogs.com
Set by avar on 16 November 2006.
chris2 hmm, is there a tool to display TAP test results from stdin? 12:13
gaal you mean parse a TAP string? I think Ovid was working on something that could do that 12:53
[particle] TAPx::Parser 14:23
avar avar@Arsia:/var/src$ pugs -e 'sub x { ... ; ??? ; !!! } say x()' 14:52
*** ... - not yet implemented at -e line 1, column 9-13
avar@Arsia:/var/src$ pugs -e 'sub x { ??? ; !!! } say x()'
*** ??? - not yet implemented at -e line 1, column 9-13
*** !!! - not yet implemented at -e line 1, column 15-19
odd sematics 14:53
[particle] what should it do? 14:54
it's die-ing
with a message that the bit of code isn't implemented
(not that the op isn't implemented) -- if i'm reading that right 14:55
allbery_b yeh. and ??? is effectively a warn instead of a die IIRC 14:56
[particle] yes 14:57
?eval sub x { ???; say 'foo'; }; say x();
evalbot_r15142 Error: Cannot cast from VUndef to Handle (VHandle) 14:57
avar [particle]: dev.perl.org/perl6/doc/design/syn/S06.html 15:08
lambdabot Title: Synopsis 6: Subroutines - perl6:
avar [particle]: skip to "yadayadayada"
I was wondering what the semantics of it were, it can probably be parsed as an expression
[particle] oh, geez, right. ... only returns false 15:09
as i see it, each one throws an exception
the ... exception is caught and returns false
??? is caught and warns 15:10
!!! is caught and dies
and, yes, i think expression is a good way to parse
[particle] (maybe !!! isn't caught at all, just propagates out) 15:12
bonesss is away: out 15:26
rindolf Hi all. 15:50
TimToady: here?
allbery_b @seen TimToady 15:51
lambdabot TimToady is in #perl6. I last heard TimToady speak 18h 51m 26s ago.
rindolf Hi allbery_b
bonesss is back (gone 01:02:32) 16:28
elmex rafl: hello? 17:15
rindolf Anyone here? 19:12
allbery_b fsvo
rindolf allbery_b: OK.
allbery_b: what is your claim to fame?
allbery_b this almost cetainly will not help you 19:13
very little
{e3} i am here!! 19:41
rindolf Hi {e3} 19:42
{e3}: what's up?
{e3} not too much. whassup with you rindolf 19:44
rindolf {e3}: I'm fine. Waiting for ABH to voice his opinion about some XML::RSS overhauls I sent him.
And without him, I cannot make any progress.
{e3} wow that is odd, i was looking at XML::RSS yesterday for no good rason 19:45
rindolf {e3}: look at the version inside the svn repository - it's much better. 19:46
{e3} haha nice, i take it that is your version?
looks nice, i will have to install now 19:49
rindolf {e3}: it's a version I heavily improved upon. 19:52
{e3}: ABH also contributed stuff to it.
{e3}: he's the CPAN maintainer.
{e3}: but I have some other stuff in mind, which I need to see if he agrees with.
{e3} i would be interested in hearing about the stuff you have in mind cause i was thinking about using this on a site 19:53
rindolf {e3}: well, they are refactorings: 19:54
{e3}: 1. Make the ending outer tags (</channel> , </item>, </image>, etc.) have consistent behaviour across all tags and RSS versions. At the moment they sometime end with \n\n and more rarely with \n. 19:56
{e3}: 2. Get rid of the AUTOLOAD method and replace it with some accessors.
{e3} cool, that would be sweet 19:57
rindolf {e3}: <<< I've been thinking of converting each version to its own class, and using the "Replace Conditional with Polymorphism" refactoring: >>> 19:58
{e3}: 4. I've been thinking of conerting the XML::Parser callbacks to be
closures, which will in turn call methods of the XML::RSS instance.
{e3}: create a class for every top-level tag that will handle the tag opening and specific generation functions, and also handle the rdf:about and rdf:resource stuff for RSS 1.0?
Ask is living in Los Angeles, right? 19:59
{e3} sounds like they are all very good ideas. i am not sure i thinks so 20:03

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!