Re: pdo wrapper API
| From: | Wez Furlong | Date: | Tue, 07 Jun 2005 12:17:54 +0000 |
| Subject: | Re: pdo wrapper API | ||
| References: | 1 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-2427@lists.php.net to get a copy of this message | ||
Sounds pretty neat. I have a couple of suggestions forming at the
back of my mind, but I'm not sure I'll find the time to share them
until after I've settled into my new place this weekend.
--Wez.
On 6/7/05, Alan Knowles <alan@akbkhome.com> wrote:
> As I mentioned before on IRC, I had to start working on a wrapper API
> around PDO, so that writing DBDO to use PDO as the backend would not
> involve me digging through the source each time I added a little work to
> it.
>
> The idea I had was to make a quasi gtk style OO wrapper around the PDO
> api, and give it a little documentation.
>
> This is the current state:
> Doc View:
>
> http://newweb.akbkhome.com/FlexySvnTest/svn.php/Doc.html?path=pecl/pdo/php_pdo_driver.h
>
> Coloured source.
>
> http://newweb.akbkhome.com/svn.php/cat.xml?path=pecl/pdo/php_pdo_driver..h
>
> obviously it's a bit of a hack at present, but do you have any thoughts
> about integrating it with PDO?
>
> php_pdo_client.c / php_pdo_client.h ?
>
>
> It uses a very simplistic documentation markup, which would be usefull
> to keep, the only 2 knock on effects at present to the source are:
> A) adding simple comments flags
> /**
> * @{type_of_block} {name_of_block}
> * some description
> **/
> B) formating the .h file definitions so they can be lined up with spaces
> in the documentation.
>
> If something like this was stored in php_pdo_client.h, I would envisage
> the structs/enums in the .h file to be #if 0 'd out so they are only
> there for documentation, not compilation..
>
>
> Thoughts.....
> Regards
> Alan
>
> --
> PECL development discussion Mailing List (http://pecl.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>