[EMAIL PROTECTED] writes:
> All,
>
> I've recently gotten involved in the lilypond cause (2 bug fixes submitted, a
> couple of features underway). My problem is I don't have a firm understanding
> of how everything comes together. I've read through the Programmer's Reference
> (PR), but it isn't
[EMAIL PROTECTED] writes:
> > lacks a lot of features that I consider necessary for comfortable
> > programming, like garbage collection, reflection and built-in strings,
> > lists, dictionaries, vectors, and first-class functions.
> >
>
> C++ does have built in strings, lists, dictionaries, and
>>* Han-Wen Nienhuys ([EMAIL PROTECTED]) wrote:
>>
>>>We have actually gotten to the point that we have a slight dislike for
>>>C++ as an implementation language. I recommend to learn Scheme and
>>
>>I'm learning C++ to use in sound synthesis programs and to be able to
>>hack lilypond. Could you sh
On Friday March 19 2004 15:25, Matevz Jekovec wrote:
> I was searching the documentation a bit for a feature which draws a
> rectangle around the certain note head (or streched around 2 notes when
> punctuated over the bar). We use this kind of arrangement, to mark a
> note that is the highest in t
Han-Wen,
On 3/19/2004 4:43 PM, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
>
>> (iterator-ctor . ,Percent_repeat_iterator::constructor)
>>
>>I'm really confused. When macro arguments are concatenated to form new tokens,
>>there should be, at minimum, some comments describing what's
Yes that's maybe the best option, I'll do that. It's just that we
list all program names at top level, and `lilypond' is the name of a
program too...
Right. So, the rule in my mind is not "all programs", it's "all
programs that are not also manual names" :).
As you probably know, th
> * lilypond: (lilypond/lilypond)Invoking LilyPond. Titling LilyPond scores.
How about simply not including that entry, and just have the top-level
entry? After all, there's no point in having it if it goes to the wrong
place.
I removed the "dvips" entry leading to "dvips invocation" fr
[EMAIL PROTECTED] writes:
>
> (iterator-ctor . ,Percent_repeat_iterator::constructor)
>
> I'm really confused. When macro arguments are concatenated to form new tokens,
> there should be, at minimum, some comments describing what's being created. And
> having an outside reference that ta
[EMAIL PROTECTED] writes:
> * Han-Wen Nienhuys ([EMAIL PROTECTED]) wrote:
> > We have actually gotten to the point that we have a slight dislike for
> > C++ as an implementation language. I recommend to learn Scheme and
>
> I'm learning C++ to use in sound synthesis programs and to be able to
> ha
I was searching the documentation a bit for a feature which draws a
rectangle around the certain note head (or streched around 2 notes when
punctuated over the bar). We use this kind of arrangement, to mark a
note that is the highest in the line (the melody climax) in our
contrapunkt class and
Han-Wen,
It wouldn't hurt. But that's not really what I'm approaching. My point wasn't
so much that the code needs to be cleaned up, but that there should be a web
page / document / something that a developer can refer to to know where to look.
In this example, I couldn't immendiately find VIRT
* Han-Wen Nienhuys ([EMAIL PROTECTED]) wrote:
> We have actually gotten to the point that we have a slight dislike for
> C++ as an implementation language. I recommend to learn Scheme and
I'm learning C++ to use in sound synthesis programs and to be able to
hack lilypond. Could you share a litte m
* Han-Wen Nienhuys ([EMAIL PROTECTED]) wrote:
> * Structure & Interpretation of Computer Programs by Abelson and
> Sussman (this book has a very wide scope, and contains way more
> information than you need for LilyPond hacking, but it's a wonderful
> book)
The full book is available here:
http:/
On Fri, Mar 19, 2004 at 02:21:49PM -0600, Douglas A Linhardt wrote:
> Thanks for your response. Your answers clarified some things and confirmed
> other things that I had come across. I will take your input and organize it a
> little better than my original questions and create some HTML pages to
[EMAIL PROTECTED] writes:
>
> Probably the biggest things that threw me are the C++ member functions that are
> declared/defined through macros. It's really annoying when a member function is
would it help if we changed VIRTUAL_COPY_CONSTRUCTOR() , ie going from
VIRTUAL_COPY_CONSTRUCTOR(Bas
[EMAIL PROTECTED] writes:
> First, let me say that I consider myself a pretty good programmer (I survived
> the layoffs at Lucent over the last few years ;) ). I am very well versed in
> C++, so of course, that's where I gravitate first when I look at Lilypond code.
> I am able to follow the Sche
About chords.
From: Tiffany Weisman
Subject: explanation
To: janneke
Here is a discussion that explains the difference, and perhaps why in
Lilypond there should be a distinction made between sus2, add2, and
add9.
http://lists.shsu.edu/pipermail/finale/2001-October/034970.html
http://lists.shsu
Han-Wen,
>
> That would be most welcome!
>
> I must admit that when I want to know how a program works, I use grep
> and emacs and dive into the source code. The comments and the code
> itself are usually more revealing than technical documents.
>
> Can you tell me where you started looking and wh
Doug,
I've also been trying to get involved with a new feature, and spent a
lot of hours trying to understand code just to answer these types of
questions. I'd like to see such a reference as well.
I'd be willing to dump whatever knowledge I have into the Lilypond
Architecture Manual (LAR?), but
[EMAIL PROTECTED] writes:
> About a year ago, I decided to learn Scheme in order to understand
> more about Lilypond.SICP was widely recommended and I shelled out
> almost $100US for it and a lab manual.
I can imagine that.
Also, I must admit I learned as much Scheme as I needed to implement
[EMAIL PROTECTED] writes:
> All,
>
> I've recently gotten involved in the lilypond cause (2 bug fixes submitted, a
> couple of features underway). My problem is I don't have a firm understanding
> of how everything comes together. I've read through the Programmer's Reference
> (PR), but it isn't
I don't think the "Structure and Interpretation of
Computer Programs" is a particularly good place to learn
Scheme.And I don't agree that it's as good a book
as many people think it is.
About a year ago, I decided to learn Scheme in order to understand
more about Lilypond.SICP was widely
Werner LEMBERG writes:
>> > I get e.g. `Easier Music Entry: No such file or directory'.
>> >
>> > So there are many dead links. Probably a bug in `info'?
>>
>> Probably someone needs/needen to run texinfo-all-menu-update. Is
>> this fixed now?
>
> No, it isn't (CVS 2004-03-19 09:10 MET).
Hmm,
Karl Berry writes:
>> * lilypond: (lilypond/lilypond)Invoking LilyPond. Titling LilyPond scores.
> How about simply not including that entry, and just have the top-level
> entry? After all, there's no point in having it if it goes to the wrong
> place.
Yes that's maybe the best option, I'll
All,
I've recently gotten involved in the lilypond cause (2 bug fixes submitted, a
couple of features underway). My problem is I don't have a firm understanding
of how everything comes together. I've read through the Programmer's Reference
(PR), but it isn't what I'm looking for.
I think what's
> > Hmm. If I now say `info lilypond', I don't see the top lilypond
> > page but `5 Invoking LilyPond', one level too deep.
>
> That is because that node name is an exact match:
>
> * lilypond: (lilypond/lilypond)Invoking LilyPond. Titling LilyPond scores.
>
> If you type `info GNU LilyPond'
On Fri, Mar 19, 2004 at 01:29:47AM +0100, Han-Wen Nienhuys wrote:
> > is it only me who can't access the CVS server at savannah.gnu.org for
> > the last three days?
[...]
> For me, it's been up again since this morning.
Thanks. I can access it again, too.
Ciao,
Kili
--
Könn't man kyrill
I have quite a lot of lilypond source that I did back in the
1.3 and 1.6.6 days. I have almost nothing that convert-ly will
process, since it usually produces errors like those below.
(By the way, this is lilypond 2.1.0, running on a Debian woody
system with some later versions of, e.g., guile.)
28 matches
Mail list logo