Anselm Lingnau wrote:
Phil Taylor wrote:
BarFly's macro processor does take lengths. You have to write
a separate macro for each length of note. The reason for this
is that an ornament which sounds right on a half note is often
wrong on an eighth.
I'm confused now. Suppose I had
[EMAIL PROTECTED] (Phil Taylor) writes:
I'm confused now. Suppose I had definitions for `Mn' and `Mn2'. What
would happen (a) for `Mc' (b) for `Mc2' (c) for `Mc4' in the body of
a tune? The interesting point is whether the `n' includes a length or
not.
(a) and (b) will expand, (c) will
On Wed, Aug 15, 2001 at 11:59:45PM +0100, Jack Campin wrote:
| I wasn't able to test the script, unfortunately. MacPerl has got itself
| into a fankle [...] Us Mac users don't have a lot of fun with perl.
| Every time I try to use it I end up concluding that it would be quicker
| to write
Phil Taylor wrote:
BarFly's macro processor does take lengths. You have to write
a separate macro for each length of note. The reason for this
is that an ornament which sounds right on a half note is often
wrong on an eighth.
I'm confused now. Suppose I had definitions for `Mn' and `Mn2'.
All right, everybody, please forget the simple-minded piece of junk I
posted recently, which suffered from the delusion of being a BarFly
macro preprocessor. As far as I am concerned here comes the Real Thing,
based on Phil Taylor's description of BarFly macros (I hope it does
everything right).
