From 069382f087fac3a01a7313830bf25a52324cd8dd Mon Sep 17 00:00:00 2001 From: fred Date: Sun, 24 Mar 2002 19:33:41 +0000 Subject: [PATCH] lilypond-0.0.36 --- Documentation/README.pod | 27 +++------------------------ Documentation/faq.pod | 30 +++++++++++++++++++++++++++++- 2 files changed, 32 insertions(+), 25 deletions(-) diff --git a/Documentation/README.pod b/Documentation/README.pod index 7126e8edc1..96c5ea4dd5 100644 --- a/Documentation/README.pod +++ b/Documentation/README.pod @@ -224,30 +224,9 @@ Do: configure make -You might want to edit Variables.make to tailor the compilation flags. -why G++ >= 2.7? LilyPond & FlowerLib uses: - -=over 5 - -=item * -builtin bool - -=item * -typeof - -=item * -operator ? - -=item * -the new for-scope - -=item * -class Rational (libg++) - -=item * -named return values - -=back +You probably want to edit Variables.make to tailor the compilation +flags. If you're not into debugging C++, then you should go for no +debugging and C<-O2> =head1 AUTHORS diff --git a/Documentation/faq.pod b/Documentation/faq.pod index b0096fd73a..d54266f053 100644 --- a/Documentation/faq.pod +++ b/Documentation/faq.pod @@ -34,7 +34,6 @@ Q: Why GPL? A: Yes. - Q: Why shouldn't I put all commands (\clef, \meter) inside the music? A: You should do what you like, but at some time we will enable @@ -50,3 +49,32 @@ A: If it is reasonable, I'll add XXXX to the TODO list. In general finding a cute syntax (such as YYYY) isn't very hard. The complicated issue how to adapt the internals to do XXXX. The parser is really a simple front end to the complicated internals. + +Q: Why do I need g++ >= 2.7? + +A: By using g++ LilyPond is portable to all platforms which support +g++ (there are quite a few). Not having to support other compilers +saves us a *lot* of trouble. LilyPond & FlowerLib uses: + +=over 5 + +=item * +builtin bool + +=item * +typeof + +=item * +operator ? + +=item * +the new for-scope + +=item * +class Rational (libg++) + +=item * +named return values + +=back + -- 2.39.5