Subject: Re: those misc thingies
>> 1. Sometimes l encounter latex errors after mudela-book, in resulting
Sorry, fixed. It was too cold near window ( open at night) for memory chip :(.
>> 4. If ( perhaps, sometimes, maybe \dots) I produce a patch ot Lily, conditionally
>> enabling ( through #ifdefs, __lilycall define etc) __attribute__ ( regparm( 3))
>> support when __i386__ defined, would it be appreciated? I know from specs and
>> experience that such __attribute__ is able to give 10-20% speedincrease in
>> programs using a lot of small/(relatively small) functions.
>> What if even add __stdcall where appropriate, and number of args is
>> known.
>> Well, the only problem I see may lie in using pointers to functions.
> I am no fan of such implementation specific tweaks. It is something
> the compiler should decide for me. Could you show me the size of the
> patch?
Not yet :( . As for specific, this is long story... gcc has -mregparm switch,
but it doesn't work in most cases due to assuming regparm calling convention
also for libc functions, kernel calls etc, which is not true for most ( all?)
linux distributions. So safest approach IMHO is #ifdefs,
say, like glibc's __P () macro, explicitly marking each func as regparmed or not...
Now I cannot do & size this, but after volume I ( if i manage this far) I'll
take a break & do it & test it also to speed my work on AMD-K590 :) .
>>> 3. Is it possible to simplify use of Lily fonts in normal texts, say
>>> for typing Ees-Major with a nice flat sign, may be through allowing
>>> such use in accents to notes through some commands, maybe in lyrics
>>> through some "magical" switch back to mudela ( or subset of mudela).
>> I don't understand what you want. Could you give an example?
> The Lilypond accidental symbols are available through the TeX macros,
> \textflat, \textsharp and \textnatural defined in the init file
thanks. solved!
August
P.S. And I should agree that pl33 sometimes breaks placement of marks & dynamics,
overlaps them sometimes and raises to close to notes ... but not to much: output
is still alive, looks & reads.
P.P.S. It can be cool in mudela-book to distinguish in pre,postMudelaExample,
whether MudelaExample is epsed or not: ( if this fragment is floating eps, than 1,
otherwise 2). say preMudelaExample[eps]{}, and change it in document body sometimes.
