I really struggled with whether I should responding to this thread any more.
I'm not trying to stir up controversy, but I hate when I'm unclear, and I end up
being misinterpretted.
I will try to keep this short, and hopefully non-controversial. And then that's
it--no more responses from me to thi
Agreed. We're off target. And I'm not trying to start a flame war. I really
don't want to start an argument. I just want to I promise not to post any more
to this thread (unless, of course I change my mind ;) ).
>
> We're going off-topic here, but I'm pretty sure that you know as well
> as I
>>* 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
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
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,
>
> 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
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
Users,
Just FYI, I'm working on a tweak to the autochange feature that would allow the
user to declare that middle C will always be in the lower staff. always in the
upper staff, or (by default) the current behavior. This is very important in
standard handbell music because middle C is always wri
Han-Wen,
On 3/15/2004 12:20 PM, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
>
>>>necessary? If not, then we can skip that option, and simply never
>>>merge if styles are different.
>>
>>I considered that, but I saw the pattern for different heads and
>>different dottings. Not having much
On 3/13/2004 6:00 PM, Han-Wen Nienhuys wrote:
> Patch looks OK in principle, but I have some further questions and comments.
>
Thanks. Any comments are appreciated.
> * Can you think of any case where merge-differently-fonted is
> necessary? If not, then we can skip that option, and simply nev
10 matches
Mail list logo
