obliterate DIGIT token class

The current patch passes regtests and removes the DIGIT token class.  It is intended for merging after review.

The choice that has been taken is that an assignment
x=-3
will not be considered as a fingering, but rather as a negative number.

After loading Documentation/snippets/creating-double-digit-fingerings.ly, you can use
x=-\finger 3
to do this instead.  The \finger music function should likely be part of Lilypond rather than just example code.  But that's a different issue.

I am not actually sure what the previous behavior would have been: the DIGIT stuff was rather inscrutable.

[Carl, 2011-09-11 12:49:46]

LGTM.

This was a clever way to solve things.  Thanks, David!

[dak, 2011-09-11 13:10:07]

Carl.D.Sorensen@gmail.com writes:

> LGTM.
>
> This was a clever way to solve things.  Thanks, David!

Actually, it took me considerable time to come up with a solution that
is boring rather than clever.

Most of my recent API additions were made in order to allow for more
boring programs.  I've gotten burnout in the TeX/LaTeX world from having
to be clever about almost anything (if you find \romannumeral in TeX
code written in the last decade, chances are that it can be traced to
one of several undesigned-for applications of this TeX primitive
established by me).

> http://codereview.appspot.com/4311041/

I am reasonably confident that this is boring enough to not cause
problems.

-- 
David Kastrup

[c_sorensen, 2011-09-11 13:18:45]

On 9/11/11 7:09 AM, "David Kastrup" <dak@gnu.org> wrote:

> Carl.D.Sorensen@gmail.com writes:
> 
>> LGTM.
>> 
>> This was a clever way to solve things.  Thanks, David!
> 
> Actually, it took me considerable time to come up with a solution that
> is boring rather than clever.

That is why I thought it was clever.  In my usage I distinguish between
"clever" and "tricky", although perhaps I shouldn't.

"Tricky" applications find clever ways to get around the intended behavior
in order to establish some desired functionality.

"Clever" applications find ways to establish the desired functionality
through straightforward application of the intended behavior.
> 
> Most of my recent API additions were made in order to allow for more
> boring programs.  I've gotten burnout in the TeX/LaTeX world from having
> to be clever about almost anything (if you find \romannumeral in TeX
> code written in the last decade, chances are that it can be traced to
> one of several undesigned-for applications of this TeX primitive
> established by me

I appreciate your desires to make things boring (or I'd say,
straightforward).  And I can see that it's often harder to fix the root
cause than to throw some special-case patch on things.

> 
>> http://codereview.appspot.com/4311041/
> 
> I am reasonably confident that this is boring enough to not cause
> problems.

Me, too.

Thanks,

Carl

[Graham Percival (old account), 2011-09-11 14:27:35]

sorry, it's a bit unclear if this is a real patch or not, due to Reitveld
screwed-up-ness.

The top of this page states this:
> Do _not_, I repeat, do _not_ merge.

I think that's left-over from your previous patch, but I don't know how to force
Rietveld to only display the commit message from the second patch.  (if that's
even possible)

Sorry for the inconvenience, but could I ask you to upload to a new rietveld
issue?  Just do
  git cl issue 0
and then do the normal steps for uploading.

[reinhold_kainhofer.com, 2011-09-11 14:36:23]

Am Sunday, 11. September 2011, 16:27:35 schrieb percival.music.ca@gmail.com:
> sorry, it's a bit unclear if this is a real patch or not, due to
> Reitveld screwed-up-ness.
> 
> The top of this page states this:
> > Do _not_, I repeat, do _not_ merge.
> 
> I think that's left-over from your previous patch, but I don't know how
> to force Rietveld to only display the commit message from the second
> patch.  (if that's even possible)

Simply go to "Edit Issue" and enter the new description...
AFAIK, this can't be done automatically with git-cl

Cheers,
Reinhold
-- 
------------------------------------------------------------------
Reinhold Kainhofer, reinhold@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org

[dak, 2011-09-11 14:56:43]

On 2011/09/11 14:36:23, reinhold_kainhofer.com wrote:
> Am Sunday, 11. September 2011, 16:27:35 schrieb percival.music.ca@gmail.com:
> > sorry, it's a bit unclear if this is a real patch or not, due to
> > Reitveld screwed-up-ness.
> > 
> > The top of this page states this:
> > > Do _not_, I repeat, do _not_ merge.
> > 
> > I think that's left-over from your previous patch, but I don't know how
> > to force Rietveld to only display the commit message from the second
> > patch.  (if that's even possible)
> 
> Simply go to "Edit Issue" and enter the new description...
> AFAIK, this can't be done automatically with git-cl

Description has been changed.