Re: Patch for documentation
| From: | Anthony Bedford | Date: | Wed, 20 Aug 2008 12:47:47 +0000 |
| Subject: | Re: Patch for documentation | ||
| References: | 1 2 3 4 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969379304@lists.php.net to get a copy of this message | ||
Hannes,
Hopefully this patch will do it.
My plan on mysqli docs is just to fill in some of the current gaps.
Unfortunately, I don't have too much time available due to several other
projects that need my attention. I'll see what I can do though.
Thanks,
Tony
Hannes Magnusson wrote:
> On Wed, Aug 20, 2008 at 13:21, Anthony Bedford <Tony.Bedford@sun.com> wrote:
>> Hi Hannes,
>>
>> Ah thanks for that.
>>
>> I've attached another diff (unified this time). Hopefully this will be a bit
>> more useable.
>
> Replace "FALSE" with "&false;" and I think its perfect.
>
>
>> I'll push on with the existing templates for now, and if I get time later
>> have a look at helping out with creating some new templates.
>
> OK.. But the "new templates" will only be useful for the mysqli
> extension, as the current templates/skeletons fit perfectly for
> regular prefix_funcname() <-> prefix::funcname() mapping.
> Like I said before, mysqli randomly uses prefix_funcname() <->
> prefix_suffix::funcname() or even prefix_suffix_funcname() <->
> prefix::suffix_funcame() and various WTFs (which is the reason I
> ignored the entire mysqli doc when I upgraded bunch of extensions
> recently).
>
> Personally, I would like to remove the current mysqli docs and start
> from scratch to get the structure right and then copy&paste content
> from the old files...
>
>
>> You've probably been asked this before - is there a whitespace
>> checking/formatting tool available?
>
> At the bottom of each file are vim modelines which bunch of editors
> support these days. Regarding "when to add \n".. I don't think we have
> scripts to check that, its just something you get used to after
> reading, and writing, couple of files :)
>
> -Hannes