i think we can start now
Tim Menzies
my goal is to make the awkcookbook a low energy project- something we
can all twiddle with for a few moments when we need a break from the
real world
that is, not some BIG task but lottsa small acorns that will one day
be a mighty forest
but we can't twiddle knobs till we have some whole machine.
so i added some machinery (e.g. a test engine, see below) and entered
in the stuff panos and mike sent me as test cases (and, hey presto,
now we have half a dozen unreviewed recipes).
i propose the following workflow :
- new entries get written to content/zYourName.awk.
- then they get reviewed (using http://code.google.com/p/awk/issues/list)
- then they get moved to the "main" files; e.g. content/strings.awk
but that's just my version0.01 ideas. you probably have better ones.
so can you all please:
1) update your local awk repos
2) have a look at what i've done on-line
3) think about the BIG picture (does my machinery make sense?). one
place to start is http://awkcookbook.info/index.cgi?write
4) have a look at the open issues, grab some of them for yourself, and
retire them (Panos- can you take care of issue #9 please?). to assign
an issue to yourself , edit it and find the "owner" field and make it
your own.
enjoy!
:-)
t
P.S. to update the site:
0) check it out. see http://code.google.com/p/awk/source/checkout
1) make changes to your local repo,
2) svn commit,
3) go to the site and click on the "update" link, top left.
P.P.S. about the test engine:
1) function names starting with an uppercase letter will get called by
the test engine
2) outputs are automatically cached in a file.
3) future calls will complain when newOutput != old)
to work the test engine, try this:
cd src; make testalll # very verbose
cd src; make score # more succinct
--
there are those who call me... tim (menzies, ph.d.)
morgantown (39.6n, -79w), usa
assoc prof csee, wvu
http://menzies.us
1-304-376-2859
PROBLEM: Handling e-mail is very very very slow, resulting in inbox overflow.
SOLUTION: Adopt the "http://four.sentenc.es" policy: no responses
longer than 4 sentences. It’s that simple. Care to try it?