On 10/9/12 8:06 AM, chengjh wrote: > The comment format can provide another way to get the whole code change > set,except svn, which is valuable for someone who has only the code base,is > not familiar with the tool svn, especially,meets regression issue related > to the code change.The comments will be quite helpful.
I agree to Pedro that we don't use such comments in our code and we shouldn't do that. We should probably cleanup the code form existing comments like this. The information is available via the SCM system and that is enough. Comments of general purpose to explain what the code is doing or to give some further explanation of the logic behind it is quite useful and good. But this kind of comments are not really useful and make the code more unreadable and doesn't really help. Juergen > > On Tue, Oct 9, 2012 at 12:04 PM, Pedro Giffuni <[email protected]> wrote: > >> Hello; >> >> --- Lun 8/10/12, chengjh ha scritto: >> >> >>> Data: Lunedì 8 ottobre 2012, 20:21 >>> I have delivered the patch >>> https://issues.apache.org/ooo/attachment.cgi?id=79748&action=diff >>> to >>> improve the graphic bullet interoperability with MS Word >>> binary document. >>> Can any expert help the code review before I commit >>> it?Thanks in advance. >>> >>> [1]Call for Test::http://s.apache.org/YYk >>> >> >> >> Please avoid comments like >> //begin fix for ixxxxxx >> ... >> //end of fix >> >> Such comments are useless and if someone does care that type of >> information is registered by the version control system (SVN) anyways. >> >> Pedro. >> > > >
