RE: [PHP-DOC] dom docs first attempt
| From: | Wez Furlong | Date: | Sat, 08 May 2004 11:24:35 +0000 |
| Subject: | RE: [PHP-DOC] dom docs first attempt | ||
| References: | 1 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969360558@lists.php.net to get a copy of this message | ||
I'm not sure that hitting the DB will be too nice on performance; it
seems much simpler just to come up with a reasonable naming convention
to resolve the ambiguity; a couple of compares are much less expensive
than the IO needed to run a query, even with SQLite being quite fast.
--Wez.
> -----Original Message-----
> From: Nuno Lopes [mailto:nlopess@php.net]
> Sent: 08 May 2004 12:19
> To: Wez Furlong; 'Derick Rethans'
> Cc: 'Rob Richards'; phpdoc@lists.php.net
> Subject: Re: [PHP-DOC] dom docs first attempt
>
> > Can we come up with a more precise naming scheme for ID
> attributes then?
> >
> > Something like function.ext-name.func-name; we can still retain (and
> > prefer) the current scheme, but use this one when we have a
> collision.
> >
> > This should be reasonably simple to hack into livedocs.
> >
> > --Wez.
>
>
> I was hacking livedocs right now to find the ID of a function
> throught the
> DB, instead of nasty search&replaces. This patch works pretty
> well now.
>
> We can implement this by querying the DB and if it returns
> more than one
> result, pick the one that is related with that extension.
> althought how will
> you choose the correct if the link is done outside of the extension?
>
> But I think that this will take too much time to execute.
> IMHO, we should
> keep the current system and just use <link>s.
>
>
> Nuno
>