On Wed, 4 Aug 2010, m...@zentific.com wrote:
> I think our definition of doxy stubs is differing here. Rather than commit > with no doxy at all and leave users clueless, I will generally write a doxy > stub, a one-liner which will at least give people some idea what it does. I > assume that other devs read the doxy as often as I do and correct errors or > fill in blanks where necessary. sure. Look at Evas and its doxy stubs. Evas has existed for something like 10 years. Did someone fix them ? No. Did they leave the user clueless ? Yes. Imho, it's not about letting the user clueless or not (the efl are not released yet), it's about being sure that we have all (most of ?) the doc filled when we release. And I think that having a big fat warning saying *where* the doc is missing is better than reading all the API to see if the doc is a stub one or not. Vincent ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
