Jack Campin wrote:
BarFly currently has an interesting bug (which probably nobody but me
has ever encountered) in which certain kinds of text at the end of a
file can screw up the processing of a tune near the start, even with
hundreds of intervening tunes. So it's not even behaving like a one-
pa
I. Oppenheim wrote:
On Tue, 8 Jul 2003, T.M. Sommers wrote:
Wil Macaulay wrote:
If I'm not mistaken, you can also embed L:, M:, and K: in the tune
proper, and I've seen N: and
I: as well.
But they can't be mistaken for notes.
Yes, they can, since H-Z can be redefined.
I guess
Wil Macaulay wrote:
If I'm not mistaken, you can also embed L:, M:, and K: in the tune
proper, and I've seen N: and
I: as well.
But they can't be mistaken for notes.
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
I. Oppenheim wrote:
On Mon, 7 Jul 2003, T.M. Sommers wrote:
These are not problems with lex and yacc specifically; any program
parsing abc will have to face them. They are ambiguities, or potential
ambiguities, in the language itself.
In the first case above, there should be no problem: the
Buddha Buck wrote:
T.M. Sommers wrote:
henrik wrote:
There is one serious problem with changing the BNF spec to literal
strings
being case sensitive - places where we don't want case sensitiveness
become horribly complicated! E.g. dor dorian DOR Dor Dorian etc
should all
be allowed, bu
henrik wrote:
There is one serious problem with changing the BNF spec to literal strings
being case sensitive - places where we don't want case sensitiveness
become horribly complicated! E.g. dor dorian DOR Dor Dorian etc should all
be allowed, but the BNF for case insensitive of that would be
("d"
Joerg Anders wrote:
Hi!
As far as I can see "abcm2ps" always connects all measure lines
over all staves.
|
---||--|||--|||--|-
---||--|||--|||--|-
---|---o---||---o---|
I. Oppenheim wrote:
> On Mon, 7 Jul 2003, Bert Van Vreckem wrote:
>
>
>> I. Oppenheim wrote:
>>
>>> If the ABC community as a whole could provide a standard
>>> complying parser, not every developer that wishes to use ABC
>>> would have to reinvent the wheel again and again. The current
>>> situati
henrik wrote:
Well, it's case sensitive. ABNF quoted strings, e.g. "A:" are not
case sensitive. ABC is (mostly) a case senstive language. So if I
want to stick to ABNF, which happens to be a standard, I'll have to
use e.g. %x58.3A and have a comment "X:" after it.
Please use strings like "A:" as yo
