Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

barbie (2653)

  reversethis-{ku. ... m} {ta} {eibrab}

Leader of [] and a CPAN author []. Co-organised YAPC::Europe in 2006 and the 2009 QA Hackathon, responsible for the YAPC Conference Surveys [] and the QA Hackathon [] websites. Also the current caretaker for the CPAN Testers websites and data stores.

If you really want to find out more, buy me a Guinness ;)

Memoirs of a Roadie []
CPAN Testers Reports []
YAPC Conference Surveys []
QA Hackathon []

Journal of barbie (2653)

Friday June 27, 2003
03:30 PM

Modules and Patches

[ #13112 ]
Fiddled around with some code last night. I started implementing some of the ideas from RichardC and JJ for Calendar::List, which is getting nearer an official CPAN release, and was relieved to see that only 3 tests failed. Now I just have to fixed that bit of code and add a few more data formats (and tests for them) and I should have another beta release.

Made some more headway with the WWW::UsePerl::Journal patch and additional Comment module. However, discovered that the comments are based on the thread they are in. This is fine if you want to find all the comments in a particular thread, but I also wanted to have a most_recent_comments() function, which could list the last 30 (or supplied number) comments added, much like the NewestNodes bit in PerlMonks. Unfortunately it doesn't work so well :(

For anyone who is interested the link to a subcomment is: ead&tid=34&pid=21409#21414

Which contains alot of info to reference the thread (sid), the parent comment (#21414), etc. However all I want is the comment itself, in this case 21409. There must be a method of doing it, but haven't had to time to look through the slash code yet. I think that'll be my task for next week now.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.