RE: Produces better error messages when programmers forget to document a property. (issue4801045)

Wed, 27 Jul 2011 03:14:31 -0700 

Hello,

)-----Original Message-----
)From: [email protected] [mailto:[email protected]]
)Sent: 27 July 2011 09:43
)To: [email protected]; [email protected];
)[email protected]; [email protected];
)[email protected]; James Lowe
)Cc: [email protected]; [email protected]
)Subject: Re: Produces better error messages when programmers forget
)to document a property. (issue4801045)
)
)On 2011/07/25 11:18:28, James.Lowe_datacore.com wrote:
)> Hello,
)
)> )-----Original Message-----
)> )From: mailto:lilypond-devel-
)[email protected]
)> )[mailto:[email protected]]
)On
)> )Behalf Of mailto:[email protected]
)> )Sent: 24 July 2011 09:41
)> )To: [email protected]; [email protected];
)> )[email protected]; [email protected]; lilypond-
)> )[email protected]; mailto:[email protected]
)> )Subject: Re: Produces better error messages when programmers
)forget
)> )to document a property. (issue4801045)
)> )
)> )On Jul 24, 2011, at 12:05 AM, mailto:[email protected] wrote:
)> )
)> )> Can you give me an idea what his does and how to test this or what
)I
)> )> am going to see as someone who runs a lot of make/reg tests?
)> )>
)> )
)> )Try adding an undocumented property to an interface (i.e. add "foo"
)to
)> )the Stem interface) and then run make.  Before, make would throw an
)> )error about procedure-name when building internals.texi.  Now, it
)will still
)> )throw that error, but before that, it'll explicitly mention that
)"foo" is
)> )undocumented, allowing for one to then document it.
)> )
)> )Cheers,
)> )MS
)
)> Thanks, for this information. I'll try to run the test tonight - I ran
)out of
)> time yesterday - so I can see what it looks like when it does what it
)is
)> supposed to do, using Neil's 'broken' patch.
)
)> James
)
)Pushed as 922d59a242646c2488738d77263580427bd7764b.
)
)Cheers,
)MS
)
)http://codereview.appspot.com/4801045/

Oh.. Didn't get a chance to test it yet :)

But I have Neil's broken patch so I can still test it tonight for my own 
personal point of view.

James

_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to