On Wed, 4 Aug 2010, m...@zentific.com wrote:
>> 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.
>
>
> Okay, now look at ecore con and its full doxy that I was able to write because
> the
>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.
Okay, now look at ecore con and its full doxy that I was able to write because
the stubs were the ONLY thing that gave me clues about how so
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 ot
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 erro
On Tue, 3 Aug 2010, Michael Blumenkrantz wrote:
> Ecore is done, I put doxy stubs in for the typedefs because I'm pressed for
> time as it is this week. If anyone who knows about the functions they're used
> in wants to spend a minute or two reading through the header to see what they
> do and
On Wed, 4 Aug 2010 09:58:30 +0900
Carsten Haitzler (The Rasterman) wrote:
>On Wed, 04 Aug 2010 09:28:01 +0900 Mike McCormack
>said:
>
>hurry up and do it... stick the typedefs in :) it won't break api/abi. just
>clean up .h's
>
>> On 08/04/2010 05:20 AM, Michael 'Mickey' Lauer wrote:
>> > Am Die
On Tue, 3 Aug 2010 13:32:58 -0400
Michael Blumenkrantz wrote:
> Hi,
>
> In my continuing crusade for documentation and readability, I've found
> one area which requires my assistance: function pointers.
> Using ecore as an example, there are currently a LOT of different
> types of function point
On Wed, 04 Aug 2010 09:28:01 +0900 Mike McCormack
said:
hurry up and do it... stick the typedefs in :) it won't break api/abi. just
clean up .h's
> On 08/04/2010 05:20 AM, Michael 'Mickey' Lauer wrote:
> > Am Dienstag, den 03.08.2010, 13:32 -0400 schrieb Michael Blumenkrantz:
> >> Short read: wi
On 08/04/2010 05:20 AM, Michael 'Mickey' Lauer wrote:
> Am Dienstag, den 03.08.2010, 13:32 -0400 schrieb Michael Blumenkrantz:
>> Short read: within the next week, function pointers within function
>> definitions will become typedefs when they are used repeatedly.
>
> Awesome. This is very welcome
Am Dienstag, den 03.08.2010, 13:32 -0400 schrieb Michael Blumenkrantz:
> Short read: within the next week, function pointers within function
> definitions will become typedefs when they are used repeatedly.
Awesome. This is very welcome for my Vala bindings, since Vala does
not support anonymous d
Hi,
In my continuing crusade for documentation and readability, I've found
one area which requires my assistance: function pointers.
Using ecore as an example, there are currently a LOT of different types
of function pointers, and they make function definitions unnecessarily
long, not to mention o
11 matches
Mail list logo
