All,

I've only written a few cookbook entries for Perl 6 / Pugs, but
there's already been plenty of feedback within the files, and it looks
like the "treat the svn like a wiki" idea might be working.

Something that stands out though is that feedback is often enough
asking for more clarification of what's going on. It would appear that
this is outside the goals of the Pleac project at present. However, I
for one am quite willing to put reasonable amount of explanation into
the Pugs cookbook tree, and I feel that it enhances the value of the
examples in many ways.

Additionally, one of the first things I realized in working through
the entries is that the individual .p6 files that I was creating are
really not runnable as a whole. For instance, a file could contain a
few separate examples, and then a sample script or two, and top it off
with an example one-liner from the command line. I briefly considered
trying to make the ones I was writing runnable, but the effort seems
to blur the examples, making them less clear and concise.

So, to explain better what's going, and to acknowledge the
unrunnability of the individual example files for the most part, I
have POD-ified (poorly, I'm not yet a god of POD) the
01strings/01-00introduction.p6 example, significantly expanding it,
adding more text, answering a question from Juerd through the
commentary, and generally making it an example driven chapter.

But before continuing in this vein, I'd like to confirm that everyone
is okay with this? It certainly makes it easier for me to express the
examples that I write, and not necessarily harder or slower to
formulate. (I'm not at all proposing that all the cookbook files have
to be that way, at least in the first pass. There's a lot of value in
just getting the examples done.)

Thanks,

Marcus Adair

Reply via email to