--- gcomnz <[EMAIL PROTECTED]> wrote: > 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 far the general consensus has been this: for each recipe in the Cookbook, try to create one file which represents the "solutions" to the problem. Trying to put things in multiple files just for one recipe will make things more difficult to manage. If some disagree, that's OK. Let's hear a better idea. In the meantime, try to keep to one file, if you can (or create something easily scriptable to merge it together for submission to pleac?). And don't worry if you can't run the examples because Pugs isn't there yet. This is partially here to show off Pugs, but it's also here to make an easy migration path for people. The real question is whether or not the Cookbook text can be used. The code is probably OK (it's meant to be reused), but the problem statements -- some of which I have copied verbatim -- are in copyright. I have a question in with O'Reilly and I've been assured that it's been forwarded to their legal department. As soon as I have an answer, I'll post it and let people know. Cheers, Ovid -- If this message is a response to a question on a mailing list, please send follow up questions to the list. Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
