Re: Macro pre-processing?

[Han-Wen Nienhuys]

Graham Percival schreef:
> In all honesty, I'm with Geoff on this one.  All the #() stuff looks 
> scary, and having the "parser location" "non-arguments" (I mean, they're 
> never referenced in the actual code) was the straw that broke my 

They are if you do real-world stuff. In particular, the location 
argument is there so you give a warning message with the correct line 
numbers, using

  (ly:input-message location "this is an error")

the "parser" argument is there so you can access parser state (eg. for 
defining new variables).

This discussion about having macros and whatnot (which inevitably comes 
with supposedly easier to understand fragments pseudo-code) is the 
umpteenth one.

Be warned that I won't accept patches that attempt to add any ad-hoc 
programming/macro language features. This has been my position for the 
last 10 years, and I don't see any reason to change it.

I recommend that people read the GUILE rationale [1] before they attempt 
to do any cute "easy" syntax design first.

[1] http://www.gnu.org/software/guile/guile.html#whatisit

  "The true cost of doing it yourself"


--

Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com