I have to agree with Derrell in his last point. A mixed solution would not help anybody because you can't trust the statements. But my general opinion differs a bit. As the framework should be API complete all the time, a non existant return statement indicates implicit that nothing will be returned. So to do the work and document (and maintain) every function which returns nothing just in case that another function is not documented correct is for me a bit overhead. Especially with the possibility to check for all left out necessary return statements with the API viewer.
Best, Martin Derrell Lipman wrote: > > On Sat, Oct 24, 2009 at 18:20, Sebastian Werner <wpba...@gmail.com> wrote: > >> >> The +1 for me was about that I would not enforce people to not comment >> them. I also would not like to remove them all, if they are already >> there. I could perfectly live with a mixed usage model here. >> > > That, to me, is the worst possible situation. Then they are truly useless, > as you can't count on them. In that case they're (sometimes, but not > always) > simply there as space fillers. Consistency IMO is the only possible > solution > here. > > Derrell > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > -- View this message in context: http://n2.nabble.com/Re-qooxdoo-commit-SF-net-SVN-qooxdoo-20405-trunk-qooxdoo-framework-source-class-qx-ui-window-Window-s-tp3849342p3891552.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
