From 85cd8f12b97f8df16b61d64797489f5943e02bec Mon Sep 17 00:00:00 2001 From: fred Date: Sun, 24 Mar 2002 19:32:37 +0000 Subject: [PATCH] lilypond-0.0.33 --- Documentation/lilygut.pod | 12 +++++++----- Documentation/lilyinput.pod | 11 +++++++---- 2 files changed, 14 insertions(+), 9 deletions(-) diff --git a/Documentation/lilygut.pod b/Documentation/lilygut.pod index e348b644d0..1ac0c5290d 100644 --- a/Documentation/lilygut.pod +++ b/Documentation/lilygut.pod @@ -25,8 +25,10 @@ No difficult algorithms. Associated datastructures have prefix Input =item 2. Processing: -Requests are processed and granted. In this step data-structures for -3. are created and filled with data: PScore, PCol, PStaff +Requests are processed and granted. This is done by three cooperating +structeres: Staff, Staff_walker and Staff_column. In this step +data-structures for 3. are created and filled with data: PScore, PCol, +PStaff =item 3. Calculation: @@ -140,11 +142,11 @@ should not be shared. The judge in this "allocation" problem is Staff (actually, it's child C). It uses the C to do most of the -work class. For each request C queries so-called +work. For each request C queries so-called Cs if they want to accept a request eg, the C will accept Cs, and turn down -Cs. If C cannot find a register wants the -request, it is junked (with a warning message). +Cs. If C cannot find a register that wants +the request, it is junked (with a warning message). After all requests have been either assigned, or junked, the Register will process the requests (which usually means creating an C or diff --git a/Documentation/lilyinput.pod b/Documentation/lilyinput.pod index b7d4888006..58a4378d4b 100644 --- a/Documentation/lilyinput.pod +++ b/Documentation/lilyinput.pod @@ -70,7 +70,10 @@ Not really crystallized; you can use '#' or '%' as line comment LilyPond first reads 'symbol.ini', which contains declarations crucial to proper operation of LilyPond (symbol tables, note names). -This language looks a lot like Rayce's which in turn owes a lot to the -POVRay raytracer. Now, I know, musictypesetting and Raytracing do not -necessarily require the same input format, but I was just to lazy to -make up a new and/or better input format. Suggestions appreciated. +This language looks a lot like Rayce's (Rayce is a raytracer that I've +written as a hobby project. I used as a practice program for writing +(among others) C++ and Yacc. It also gave me RSI :-( ) which in turn +owes a lot to the POVRay raytracer. Now, I know, musictypesetting and +Raytracing do not necessarily require the same input format, but I was +just to lazy to make up a new and/or better input format. Suggestions +appreciated. -- 2.39.5