> [...] it may be feasible to remove the line
>
> if (Super::print_smob != 0)
>
> in lily/include/smobs.hh. Can you check whether this solves your
> problem or whether warnings for other functions remain?
Other warnings remain. I've applied the following patch to make
compilation silent ag
On 2014/10/04 04:12:14, Dan Eble wrote:
It's verbose, but it does the trick portably (I think).
Too clever. I don't want to obfuscate the code like that (bringing type
overloading into play) just to dance around a warning. print_smob does
not need a check: we'll always set something other tha
Reviewers: ,
Message:
It's verbose, but it does the trick portably (I think).
Description:
Eliminate "will never be null" warnings in smobs.tcc.
Please review this at https://codereview.appspot.com/153970043/
Affected files (+41, -6 lines):
M lily/include/smobs.tcc
Index: lily/include/smob
Werner LEMBERG writes:
> [release/2.19.15-1-13-gdd5a6e7]
> [gcc 4.7.2]
>
> Compiling lilypond, I now get zillions of warnings like this:
>
> In file included from ./include/smobs.hh:315:0,
>from ./include/box.hh:10,
>from ./include/font-metric.hh:23,
>
Hi James
This is definitely a big improvement, but I have a serious concern over
the confusion you've introduced about what is supported in basic
LilyPond and what is added by the articulate script. I've tried to
indicate places where this confusion appears. The clear statement
currently shown
[release/2.19.15-1-13-gdd5a6e7]
[gcc 4.7.2]
Compiling lilypond, I now get zillions of warnings like this:
In file included from ./include/smobs.hh:315:0,
from ./include/box.hh:10,
from ./include/font-metric.hh:23,
from ./include/font-int
Thanks.
https://codereview.appspot.com/120480043/diff/140001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
https://codereview.appspot.com/120480043/diff/140001/Documentation/notation/input.itely#newcode2784
Documentation/notation/input.itely:2784: @q{Articu
That is very exciting. I wrote a graduate paper integrating LilyPond and
Gregorio with a LaTeX document, and it was very rewarding. The most beautiful
document I've written (visually, that is). I look forward to reading this
paper. (Provided it will be in English; if not, I'll have my priests
2014-10-03 12:52 GMT+02:00 Davide Liessi :
> "LilyPond: un music engraver integrabile LaTeX"
Typo: the Italian title is "LilyPond: un music engraver integrabile con LaTeX".
Best wishes.
Davide
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http
"Phil Holmes" writes:
> - Original Message -
> From: "Davide Liessi"
> To: ;
> Cc: "Tommaso Gordini"
> Sent: Friday, October 03, 2014 11:52 AM
> Subject: Paper on music engraving, LilyPond and LaTeX at GuIT meeting 2014
>
>
>> Dear all,
>>
>> this summer I've been working with Tommaso
- Original Message -
From: "Davide Liessi"
To: ;
Cc: "Tommaso Gordini"
Sent: Friday, October 03, 2014 11:52 AM
Subject: Paper on music engraving, LilyPond and LaTeX at GuIT meeting 2014
Dear all,
this summer I've been working with Tommaso Gordini on a paper titled
"LilyPond: un mus
Dear all,
this summer I've been working with Tommaso Gordini on a paper titled
"LilyPond: un music engraver integrabile LaTeX" ("LilyPond: a music
engraver which can be integrated with LaTeX").
The paper, written in Italian, is composed of three parts.
In the first, we describe the peculiar trait
https://codereview.appspot.com/120480043/diff/140001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
https://codereview.appspot.com/120480043/diff/140001/Documentation/notation/input.itely#newcode2784
Documentation/notation/input.itely:2784: @q{Articulate} scr
Thanks Valentine
https://codereview.appspot.com/120480043/diff/140001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
https://codereview.appspot.com/120480043/diff/140001/Documentation/notation/input.itely#newcode2654
Documentation/notation/input.ite
14 matches
Mail list logo
