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 ]

masak (6289)

  (email not shown publicly)

Been programming Perl since 2001. Found Perl 6 somewhere around 2004, and fell in love. Now developing November (a Perl 6 wiki), Druid (a Perl 6 board game), pls (a Perl 6 project installer), GGE (a regex engine), and Yapsi (a Perl 6 implementation). Heavy user of and irregular committer to Rakudo.

Journal of masak (6289)

Sunday August 02, 2009
02:32 PM

Week 12 of -- a spec and smartlinks

[ #39392 ]
Moses all growup now!. Wun dayz he go see his frenz. they is workin hard. Moses seez sum Gypshun d00d beatin up a Joo laik Mosis. Mosis look round & not see no 1 and he go and pwnd teh Gypshun. He sed b00m hed shot but qu1et laik. He hided teh bodi in sand to makes it invisabl bodi. — Exodus 2:11-12

Very brief, because I'm on vacation:

For the past week, I've had the idea to hook up smartlinks in the tests of, and then generate spec HTML files from spec Pod files. (Just like the Perl 6 project does.)

I've succeeded in generating the HTML, thanks to a pre-packaged Text::SmartLinks module, that only required a few tweaks to do exactly what I want. Here's the spec for the Astaire sub-project, which got started at the same time I had this idea.

Now, ideally we'd also like test statistics in the HTML files, tracking the implementation progress. There are scripts in the Pugs directory for doing this, but they are... written by clever people. Meaning I don't see what I should change to have this code work for me.

To make the question very concrete (in case someone out there has the know-how and tuits to help me): how to I smoke my tests and generate a smoke.yml file which I can then feed into the Text::SmartLinks process?

I wish to thank The Perl Foundation for sponsoring the effort.

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.