Seriously, read, reread and reread lilygut and CodingStyle, and
just start anywhere.
+Anywhere? Well, most of the comment doco are in the header files, so
+your best bet would be C<less lily/include/*.hh>. Some of the most
+important data-structures are to be found in:
+
+ - p-col.hh
+ - *request.hh
+ - register.hh
+ - score-elem.hh
+ - input-music.hh
+ - linespace.hh
+ - item.hh
+ - spanner.hh
+ - voice.hh
+
+
Q: Why GPL?
A: Yes.
/*
- input-score.hh -- declare
+ input-score.hh -- declare Input_score
- source file of the LilyPond music typesetter
+ source file of the GNU LilyPond music typesetter
(c) 1997 Han-Wen Nienhuys <hanwen@stack.nl>
*/
#define INPUTSCORE_HH
#include "varray.hh"
-#include "proto.hh"
+#include "lily-proto.hh"
#include "plist.hh"
#include "string.hh"
#include "input.hh"
/*
- lyric-register.hh -- declare
+ lyric-register.hh -- declare Lyric_register
- source file of the LilyPond music typesetter
+ source file of the GNU LilyPond music typesetter
(c) 1997 Han-Wen Nienhuys <hanwen@stack.nl>
*/
#include "register.hh"
#include "varray.hh"
-#include "proto.hh"
+#include "lily-proto.hh"
+
class Lyric_register : public Request_register {
Array<Lyric_req*> lreq_arr_;
virtual bool acceptable_request_b(Request*);
/*
- midi-def.hh -- declare
+ midi-def.hh -- declare Midi_def
- source file of the LilyPond music typesetter
+ source file of the GNU LilyPond music typesetter
(c) 1997 Jan Nieuwenhuizen <jan@digicash.com>
*/
#ifndef MIDIDEF_HH
#define MIDIDEF_HH
-#include "proto.hh"
+#include "lily-proto.hh"
#include "real.hh"
#include "string.hh"
#include "moment.hh"
/*
- registergroup.hh -- declare
+ registergroup.hh -- declare Register_group_register
- source file of the LilyPond music typesetter
+ source file of the GNU LilyPond music typesetter
(c) 1997 Han-Wen Nienhuys <hanwen@stack.nl>
*/
#include "plist.hh"
-#include "staff-elem-info.hh"
+#include "score-elem-info.hh"
#include "register.hh"
/**