that I don't get the forward declaration
error?
It's not possible. A vectorX internally creates a pointer to X,
which is why it doesn't need to know about X, but drul_array doesn't
work like that.
Just include stencil.hh and be done with it.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
, that might be less necessary.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
multiple floating point ops (add, multiply, etc.)
On Thu, Feb 9, 2012 at 9:24 PM, m...@apollinemike.com
m...@apollinemike.com wrote:
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
to minimize: comments easily are
forgotten when changing code, so they tend go out of date faster.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman
for
yourself by walking up the call-chain until you find the function that
populates the variable.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman
over #1,
since the grace note code is small but difficult and tricky to
understand. It's much more complicated than the note collision code,
for example.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing
:
Right.
I've just looked at the part combiner code, and it creates complex GOOPS
We're talking about the note collision code, though.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel
and access them from the Scheme module.
My idea is was to abstract the concrete list away.
There is no strong reason for that though, so if you want to change
it, feel free.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond
to post the before and after PDFs of such a transition?
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ultimately?
Without knowing more, I suspect this data should be computed at font
generation time, and it should be embedded in the OTF file.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond
. You
could do whatever format works best for you; since the font is only
read once, you don't have to worry about performance when loading it.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond
project
with no independent legal body to take the $500; what happens to
that money? question?
I think FSF/GNU project can and has acted as organization in the past.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel
infrastructural changes (which may depend on what
people wind up asking for after the change).
I'd rather not introduce more fragility (cf the generated .scm files)
into the build process which is complicated enough as it is. I think
users can wait for another week if need be.
--
Han-Wen Nienhuys
On Fri, Feb 17, 2012 at 10:49 AM, Han-Wen Nienhuys hanw...@gmail.com wrote:
On Fri, Feb 17, 2012 at 6:00 AM, m...@apollinemike.com
m...@apollinemike.com wrote:
This sounds wrong. Where does this data come from ultimately?
The svg files. I read them into lilypond and generate
On Tue, Feb 21, 2012 at 7:17 PM, Janek Warchoł janek.lilyp...@gmail.com wrote:
In another thread Han-Wen wrote:
On Fri, Feb 17, 2012 at 1:58 PM, Han-Wen Nienhuys hanw...@gmail.com wrote:
Also, nowadays, fontforge supports Python scripting. We could redo all
the craziness involving generated
Metatype in the TeX world, and it has
been used for generating various Type1 fonts from Metafont sources.
This looks very outdated, and it seems to use autotrace. We abandoned
traced outlines for exact conversions a few years ago.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
extension
only, then we don't need to worry about graphic toolkits and such.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond
if
the difference is less than X percent.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
letter
interlock with a note stem can improve the overall arrangement.
Exactly my point: you can fix the single letter case with a single
bbox per glyph. Why do you need more accuracy than single box per
glyph?
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
On Thu, Mar 1, 2012 at 8:01 AM, David Kastrup d...@gnu.org wrote:
Han-Wen Nienhuys hanw...@gmail.com writes:
2012/3/1 Janek Warchoł janek.lilyp...@gmail.com:
From what i see, the skylines are now more precise than they need to
be - every glyph has a skyline of 10 or so boxes, even if it's
it. I could put is before the exception, but
this is different from the style on the existing code.
try running lilypond --verbose
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel
://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/faqs#goals
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond
not into the project, so it
is good to be conservative with applying them. That said, I think a
macro for this pattern is justified given its frequency of appearance.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing
] - previous[d][LEFT]
perhaps this will set rods too large if you have lots of ledgered
chords with seconds in them, in a tight spacing configuration.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond
for its own good.
FYI, my experience is that writing this type of code involves cut
paste, and it is easy to make errors like
if (some_new_event_)
mark(the_event_i_copied_it_from_)
I agree that 4 is borderline small enough not to use a loop.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
and it didn't go through. I'll have to change e-mail
addresses on the list...
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl
=_blank
href=http://www.ensemble101.frgt;herelt;/agt; to learn more!
/tweet
/tweets
http://codereview.appspot.com/6068045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen
Who is GNU_LilyPond anyway? I thought it was, but I might be mistaken.
On Fri, Apr 27, 2012 at 9:39 AM, Graham Percival
gra...@percival-music.ca wrote:
On Fri, Apr 27, 2012 at 09:19:55AM -0300, Han-Wen Nienhuys wrote:
Is it possilble to display the contents of the twitter #lilypond
hashtag
On Fri, Apr 27, 2012 at 10:15 AM, Han-Wen Nienhuys hanw...@gmail.com wrote:
Who is GNU_LilyPond anyway? I thought it was, but I might be mistaken.
I mean: I thought it was Jan.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
of a suitable license for open source fonts?
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
[correct Jan's address]
On Mon, Apr 30, 2012 at 5:02 PM, Han-Wen Nienhuys hanw...@gmail.com wrote:
On Mon, Apr 30, 2012 at 3:21 PM, Janek Warchoł janek.lilyp...@gmail.com
wrote:
I'm trying to use the nice Feta braces in an OpenType math font I'm
working on[1] that is licensed under OFL which
.
This is not untrue... :)
Bottom line - CONGRATS TO EVERYONE. This is the most prestigious open-source
music software competition in the world. Get excited!
Congrats to everyone, including myself!
(isnt it the *only* open-source music software competition in the world? :-)
--
Han-Wen Nienhuys - han
of elegance, but
unless you can measure it makes any difference, we shouldn't bother
optimizing it.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman
a
Beam after the real end point has already passed. However, wouldnt it
be easier to simply use manual beams in the example? Putting a
footnote on something automatically generated sounds like a bad
practice, since it stops making sense when you alter the autobeaming
rules.
--
Han-Wen Nienhuys
, with an option to try using it
without doing a complete GUB build.
it would be best if make dist were rewritten to take git's idea of
the tree, and then add any necessary generated files (eg. configure,
README) to that.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman
caused by
discussing things in a hurry over e-mail, and were always resolved
when we called to discuss things over the telephone.
I warmly recommend getting together, hacking, thinking and drinking
some beer (or whatever your preferred beverage).
Are you with me?
--
Han-Wen Nienhuys - han
that align on parents should usually have something more
specific as X-parent (eg. a notehead).
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo
be OK. FSF's beef is with restrictive licensing, since
licensing means you cannot freely copy the software (share with your
neighbors).
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel
?
Hall as to who does it next, or whether he wants to give you admin
on the issue tracker so that you can do it.
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen
code due to trying to
manually simulate rational arithmetic and getting it wrong.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond
cost. Cleaning it up is
only worthwhile if you intend to do further work (ie. more syntax
changes) on it.
* people that don't use Lily now probably do for lack of a graphical interface.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
(set them to the ts from the latest git commit for
example).
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
distinguish
between
\times 2/3 { c4 c4 c4 c4 c4 c4 }
and
\times 2/3 { c4 c4 c4 } \times 2/3 { c4 c4 c4 }
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org
On Sat, Aug 4, 2012 at 3:41 PM, Han-Wen Nienhuys hanw...@gmail.com wrote:
Hi Felipe,
I got go-enc2ly such that it prints useful output for simple scores (try eg.
http://www.samba-choro.com.br/partituras/porartista/vermusica?mid=8544pos=156
); there are some installation instructions
believe the android build works like this, so it should be doable.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
this in to
the code rather straightforwardly. If you only have to do it once per
line, the spacing computation is actually pretty cheap, so you get
most of the benefit with just this information.
You can use Scheme data structures as a data format.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl
anyone have the same feeling? And please take look
at the atachment - this is how perfect flags should look like to me.
In your example, the top hook looks larger than the other ones,
especially in 32, 64 and 128, because it has nothing above it.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
Warchoł janek.lilyp...@gmail.com wrote:
Hey all,
attached example might be a better-looking suggestion of
non-christmas-tree flags ;)
I'd be happy to Metafont them as an optional font variant - if someone
writes the architecture.
cheers,
Janek
--
Han-Wen Nienhuys - han...@xs4all.nl - http
generators
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
:
Author: Aleksandr Andreev aleksandr.andr...@gmail.com
Author: Bertrand Bordage bordage.bertr...@gmail.com
Author: Carl Sorensen c_soren...@byu.edu
Author: Carsten Steger carsten.ste...@googlemail.com (*)
Author: Glen Prideaux glenpride...@iname.com
Author: Han-Wen Nienhuys han...@xs4all.nl
Author: Janek
by.
Main development team:
Bertrand Bordage, Trevor Daniels, Phil Holmes, Ian Hulin, Reinhold
Kainhofer, David Kastrup, Jonathan Kulp, Werner Lemberg, John
Mandereau, Patrick McCarty, Joe Neeman, Han-Wen Nienhuys, Jan
Nieuwenhuizen, Graham Percival, Mark Polesky, Neil Puttock, Mike
Solomon, Carl
to be smaller so that the
slur was less bound to the edges.
AFAICS, this is designed so the ends of the slur stay close to base_attachment_
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond
-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org
with this approach.
Best,
John
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
another list. Also,
finding the discussion later on will be easier if it happens on
lilypond-devel.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman
are going to produce a *lot* of emails.
And if they come to conclusions, they are going to produce effects on
everybody. Including people using LilyPond as a service.
Before we go around proposing solutions, it would be good to know what
problems we are trying to solve.
--
Han-Wen Nienhuys - han
-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
, and
making sure existing situations stay the same.
best,
Janek
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
of
thought. It may or may not be a great idea.
These ideas are obviously not fully fleshed out, but this makes
a good example of the meta-discussion of how we want to organize
the discussion of such ideas.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
are giving Perl while we are
discussing readability./offtopic
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
to be used without side-effects, so there is a little
difference between a function and a built-in input language construct,
such as \times.
I think in Perl you can have functions
look like dead statements, but that's probably just making the argument
better.
--
Han-Wen Nienhuys - han
URL:http://code.google.com/p/lilypond/issues/detail?id=2067 and leads
to behavior surprising to users.
Why should this be in a music function at all? If the user knows
enough scheme to understand that port means file, he would be expert
enough to write the expression in Scheme anyway?
--
Han-Wen
On Sat, Sep 1, 2012 at 8:27 AM, David Kastrup d...@gnu.org wrote:
Graham Percival gra...@percival-music.ca writes:
On Fri, Aug 31, 2012 at 11:11:28PM -0300, Han-Wen Nienhuys wrote:
I have become convinced that optional, unnamed arguments are not a
happy design decision, in any language
On Sat, Sep 1, 2012 at 11:42 AM, Han-Wen Nienhuys hanw...@gmail.com wrote:
\tempo \markup{ Presto } 4. = 172 ~ 188
c1 c
}
While this might be a mess for the parser to sort out it is perfectly
understandable for a musician trying to write his/her music.
This is also the danger of having
On Sat, Sep 1, 2012 at 8:11 AM, Graham Percival
gra...@percival-music.ca wrote:
On Fri, Aug 31, 2012 at 11:11:28PM -0300, Han-Wen Nienhuys wrote:
I have become convinced that optional, unnamed arguments are not a
happy design decision, in any language. In Lily it's particularly
problematic
that hasn't been agreed on explicitly. I would
nowadays hold that it is actually better to have different function
names, and have the user be explicit about what he is doing.
The discussion about syntax changes is not going to work unless we
know in what direction we want to go.
--
Han-Wen
to remove them in the future.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
already, but I guess I am mistaken?
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Sat, Sep 1, 2012 at 12:04 PM, David Kastrup d...@gnu.org wrote:
Han-Wen Nienhuys hanw...@gmail.com writes:
On Sat, Sep 1, 2012 at 8:27 AM, David Kastrup d...@gnu.org wrote:
It is reasonably easy to state this will have to go. However, I have
not so far attempted a replacement since I am
with -DDEBUG_BEAM_SCORING=1
this is the default already; see include/main.hh
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
with virtually no changes. I guess that such is life.
Of course many of our ideas will not be good. That's fine!
That's how creative thinking works!
No; syntax discussions without understanding how the lilypond parser
works is just blowing around hot air and discussing bike shed colors.
--
Han-Wen
and conciseness of the current
format.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
. If a proposer manages to get that far, I
promise I will take a serious look at it.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond
. I have been dealing with syntax changes and
improvements for many years; and it is tiring. Why can't people see
the world from our perspective for a change?
I mean, what possible downsides are there to this? It will be
I have only so much time. Don't waste it with fluffing around.
--
Han-Wen
On Mon, Sep 3, 2012 at 9:00 AM, Graham Percival
gra...@percival-music.ca wrote:
On Mon, Sep 03, 2012 at 01:24:22AM -0300, Han-Wen Nienhuys wrote:
On Sat, Sep 1, 2012 at 4:39 PM, Graham Percival
gra...@percival-music.ca wrote:
The meta-target is after spending 5 years very publicly
telling
make some things easier to get done with. With
regard to _designing_ the language of LilyPond, I think we are better
off discussing and relating our goals, and seeing where this takes
development.
+1
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
On Mon, Sep 3, 2012 at 9:03 AM, David Kastrup d...@gnu.org wrote:
Graham Percival gra...@percival-music.ca writes:
On Mon, Sep 03, 2012 at 02:20:43AM -0300, Han-Wen Nienhuys wrote:
To me, a Grand Input Syntax fixing of LilyPond, would amount to
creating a syntax that strictly separates
On Mon, Sep 3, 2012 at 11:46 AM, David Kastrup d...@gnu.org wrote:
I actually remembered one thing that remains worth doing: integrating
\chordmode into \notemode.
This sounds like a nice project. I am still worried by the backward
compat breakage, though. Is it worth it?
--
Han-Wen Nienhuys
it is parsing, evaluating it interpretation.
Ouch. Sound like something we seriously don't want at all.
Right - this means that we seriously don't want to be a music
interchange/storage format.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
functions, right?
Correct.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
.
Such considerations make me skeptic of changes that are explained by
way of example, especially if they have a broad impact. Such changes
can often not be implemented sanely.
If I missed your point, can you state it more explicitly?
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
explanation.
Isn't this an argument for delimiting the argument list?
It is. The disadvantage is that it breaks all existing files.
If you don't expect
anyone to guess where it begins and ends correctly (and I didn't), doesn't
that mean we should have a more explicit syntax?
--
Han-Wen
On Tue, Sep 4, 2012 at 3:40 PM, Janek Warchoł janek.lilyp...@gmail.com wrote:
On Tue, Sep 4, 2012 at 5:54 PM, Han-Wen Nienhuys hanw...@gmail.com wrote:
Isn't this an argument for delimiting the argument list?
It is. The disadvantage is that it breaks all existing files.
I think i remember
the functionally, even better.
But if we are to have a discussion about syntax let's first list the problems
we need to solve, and reach agreement on which ones need to be tackled.
Then we know what it is we are trying to optimise.
I completely support this analysis.
--
Han-Wen Nienhuys - han
Beam_scoring_problem::solve(); the first number is the index of
the chosen solution, the second the number of candidates.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https
On Tue, Sep 4, 2012 at 6:25 PM, Han-Wen Nienhuys hanw...@gmail.com wrote:
Isn't this an argument for delimiting the argument list?
It is. The disadvantage is that it breaks all existing files.
I think i remember one of the developers saying we should also care
for future users, and that's
with.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
way possible, a business model which
makes ever less sense in the digital age.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond
On Sat, Sep 8, 2012 at 12:00 PM, David Kastrup d...@gnu.org wrote:
Han-Wen Nienhuys hanw...@gmail.com writes:
On Fri, Sep 7, 2012 at 4:42 AM, David Kastrup d...@gnu.org wrote:
There's one thing worth clarifying: when i say syntax changes, i
mean changes in how user input looks like. So
that, and in general
conservative GC cannot guarantee that. Conservative GC is problematic
if the heap is large compared to the address space; everything then
starts looking like a pointer.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
before making any decisions. The everything postfix decision
was made after I had to copy music, and realized how jarring it was to
have to remember what goes where when copying music; I fear that your
proposal will require remembering more details.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
with this type of polymorphism.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Wed, Sep 12, 2012 at 12:04 PM, David Kastrup d...@gnu.org wrote:
Han-Wen Nienhuys hanw...@gmail.com writes:
On Wed, Sep 12, 2012 at 5:38 AM, David Kastrup d...@gnu.org wrote:
Hi,
if we write xxx in LilyPond, this is considered to be a string. I want
xxx.yyy.zzz to be a list of strings
and takes an hour of extra time.
I would argue that this is an indication that the \tempo syntax is a
mistake. If making backward incompatible changes is allowed, I would
suggest to reconsider and scrap the onerous parts of its syntax.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl
,
as it will have compatiblility implications.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
pointers
have to be stored both ways (including inverting 1-N relations into
N-1 relations), and the both-way links have to be rewritten correctly
during line breaking.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
lilypond
On Wed, Sep 26, 2012 at 10:40 PM, David Kastrup d...@gnu.org wrote:
Han-Wen Nienhuys hanw...@gmail.com writes:
In order to do cache invalidation, you will have to construct the
reverse graph. If A.x depends on B.y, now A points to B. For proper
cache invalidation, if B.y changes, then A.x
On Sat, Sep 29, 2012 at 11:35 AM, m...@mikesolomon.org
m...@mikesolomon.org wrote:
On 29 sept. 2012, at 10:59, Han-Wen Nienhuys hanw...@gmail.com wrote:
On Wed, Sep 26, 2012 at 10:40 PM, David Kastrup d...@gnu.org wrote:
Han-Wen Nienhuys hanw...@gmail.com writes:
In order to do cache
1 - 100 of 3768 matches
Mail list logo
