Re: proposals for LM B. Scheme tutorial

2009-06-21 Thread Trevor Daniels
Mark Polesky Saturday, June 20, 2009 9:17 PM Here are some proposed additions to LM B. Scheme tutorial These are things that I wished I knew when I was starting! I haven't made a patch because I want to get feedback from you guys first. Thanks - Mark Happy to add these as soon as you arrive

Re: proposals for LM B. Scheme tutorial

2009-06-21 Thread Mark Polesky
Nicolas Sceaux wrote: > Where it puts that parens alone are a rare exception. > Remember that you're writing a tutorial. Using a good, > consistent style is primordial, so that users that learn > from it may in turn use a good style. It's a pain to > read badly formatted code. I respectfully agr

Re: proposals for LM B. Scheme tutorial

2009-06-21 Thread Nicolas Sceaux
Le 20 juin 09 à 23:18, Mark Polesky a écrit : Nicolas Sceaux wrote: #(begin (define foo 0) (define bar 1) ) The formatting is bad. #(begin (define foo 0) (define bar 1)) Parentheses are never left alone on a line. I respectfully* disagree: http://community.schemewiki.org/

Re: proposals for LM B. Scheme tutorial

2009-06-20 Thread Carl D. Sorensen
On 6/20/09 3:18 PM, "Mark Polesky" wrote: > > > Nicolas Sceaux wrote: >>>#(begin >>> >>>(define foo 0) >>>(define bar 1) >>> >>>) >> >> The formatting is bad. >> >>> #(begin >>>(define foo 0) >>>(define bar 1)) >> >> Parentheses are never left alone on a line. >

Re: proposals for LM B. Scheme tutorial

2009-06-20 Thread Werner LEMBERG
>> The formatting is bad. >> >> > #(begin >> >(define foo 0) >> >(define bar 1)) >> >> Parentheses are never left alone on a line. > > I respectfully* disagree: [...] Well, putting trailing parentheses into separate lines is useful while writing code -- I do this too, but finally they get

Re: proposals for LM B. Scheme tutorial

2009-06-20 Thread Carl D. Sorensen
On 6/20/09 2:17 PM, "Mark Polesky" wrote: > > > Here are some proposed additions to LM B. Scheme tutorial Good for you! Thanks! > > ***new paragraph and example: > Multiple consecutive scheme expressions in a music file can be > combined using the *begin* operator. This reduces the numbe

Re: proposals for LM B. Scheme tutorial

2009-06-20 Thread Mark Polesky
Nicolas Sceaux wrote: > >#(begin > > > >(define foo 0) > >(define bar 1) > > > >) > > The formatting is bad. > > > #(begin > >(define foo 0) > >(define bar 1)) > > Parentheses are never left alone on a line. I respectfully* disagree: http://community.schemewiki.org/?scheme

Re: proposals for LM B. Scheme tutorial

2009-06-20 Thread Jonathan Kulp
Graham Percival wrote: LGreatTM! Cheers, - Graham +1! Thanks for helping everyone else learn from your experience. (and for your sweet scheme hacks!) Jon On Sat, Jun 20, 2009 at 01:17:02PM -0700, Mark Polesky wrote: Here are some proposed additions to LM B. Scheme tutorial These are th

Re: proposals for LM B. Scheme tutorial

2009-06-20 Thread Nicolas Sceaux
Le 20 juin 09 à 22:17, Mark Polesky a écrit : ***new paragraph and example: Multiple consecutive scheme expressions in a music file can be combined using the *begin* operator. This reduces the number of hash marks to one. However, within such a combined expression, LilyPond comments ("%" and "%{

Re: proposals for LM B. Scheme tutorial

2009-06-20 Thread Graham Percival
LGreatTM! Cheers, - Graham On Sat, Jun 20, 2009 at 01:17:02PM -0700, Mark Polesky wrote: > > Here are some proposed additions to LM B. Scheme tutorial > > These are things that I wished I knew when I was starting! I > haven't made a patch because I want to get feedback from you guys > first. >

proposals for LM B. Scheme tutorial

2009-06-20 Thread Mark Polesky
Here are some proposed additions to LM B. Scheme tutorial These are things that I wished I knew when I was starting! I haven't made a patch because I want to get feedback from you guys first. Thanks - Mark ***(I'm leaving this paragraph as it is) LilyPond uses the Scheme programming language, bo