Re: Coding practices

> Quite a good source of good coding is the Linux kernel IMHO. And probably most of the GNU projects, e.g. `Emacs' or `coreutils'. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Coding practices

> I would suggest to code like that Chinese programmer, so that any > questions regarding the code will get a plausible "Let's see, what > was I thinking here? Wait, I remember this was a bit more complex, > be back in a minute." reply, with your "partner" actually being able > to be back in a min

Re: Coding practices

Han-Wen Nienhuys writes: > On Sat, Feb 16, 2013 at 3:46 PM, David Kastrup wrote: > >> I was talking about "reasonable documenting and coding practice". >> That does not involve how to structure things. As I said, we are >> talking about post-1960s Pascal coding, and he tried his best to >> stil

Re: Coding practices

Le 16 févr. 2013 à 15:15, m...@mikesolomon.org a écrit : > I've heard from friends that Google has codified standards for how code > should be written. What are these standards like? Style guides for Google-originated open-source projects ___

Re: Coding practices

On Sat, Feb 16, 2013 at 3:15 PM, m...@mikesolomon.org wrote: Rather than letting this continue to be problematic, I'd like to establish a sort of GLISS for LilyPond coding style. We would discuss certain conventions in the codebase to see where commonalities lie in the codebas

Re: Coding practices

On Sat, Feb 16, 2013 at 3:46 PM, David Kastrup wrote: >>> If you want an example of reasonable documenting and coding practice, >>> take tex.web (it is public domain), run it through weave and pdftex >>> and peruse significant extracts of the resulting PDF. >> >> While tex.web is a beautiful examp

Re: Coding practices

Han-Wen Nienhuys writes: > On Fri, Feb 15, 2013 at 10:44 PM, David Kastrup wrote: > >> If you want an example of reasonable documenting and coding practice, >> take tex.web (it is public domain), run it through weave and pdftex >> and peruse significant extracts of the resulting PDF. > > While t

Re: Coding practices

On 16 févr. 2013, at 16:06, Han-Wen Nienhuys wrote: > On Fri, Feb 15, 2013 at 10:44 PM, David Kastrup wrote: >>> After reading over David's most recent e-mails to the list, it is >>> clear to me that there is a coding-practice debt in LilyPond. >>> Standards of how and when to do certain things

Re: Coding practices

On Fri, Feb 15, 2013 at 10:44 PM, David Kastrup wrote: >> After reading over David's most recent e-mails to the list, it is >> clear to me that there is a coding-practice debt in LilyPond. >> Standards of how and when to do certain things are not shared across >> all programmers, and things that s

Re: Coding practices

On 15 févr. 2013, at 23:44, David Kastrup wrote: > "m...@mikesolomon.org" writes: > >> Hey all, >> >> After reading over David's most recent e-mails to the list, it is >> clear to me that there is a coding-practice debt in LilyPond. >> Standards of how and when to do certain things are not sha

Re: Coding practices

Francisco Vila writes: > 2013/2/15 David Kastrup : >> If you want an example of reasonable documenting and coding practice, >> take tex.web (it is public domain), run it through weave and pdftex and >> peruse significant extracts of the resulting PDF. > > Couldn't resist. "Literate programming",

Re: Coding practices

2013/2/15 David Kastrup : > If you want an example of reasonable documenting and coding practice, > take tex.web (it is public domain), run it through weave and pdftex and > peruse significant extracts of the resulting PDF. Couldn't resist. "Literate programming", they call it, right? Being in th

Re: Coding practices

"m...@mikesolomon.org" writes: > Hey all, > > After reading over David's most recent e-mails to the list, it is > clear to me that there is a coding-practice debt in LilyPond. > Standards of how and when to do certain things are not shared across > all programmers, and things that seem commonsens