RE: [PHP-PEAR] PEAR Status
| From: | Seth Fitzsimmons | Date: | Mon, 26 Jun 2000 14:13:36 +0000 |
| Subject: | RE: [PHP-PEAR] PEAR Status | ||
| References: | 1 | Groups: | php.pear |
| Request: | Send a blank email to php-pear+get-125@lists.php.net to get a copy of this message | ||
I grabbed your changes from CVS over the weekend (after reading your message
with IMP ;-) and played around with them a bit. They seem to work fine,
though I haven't actually done anything with the fetchRow() stuff (I'm going
to assume it works). Your changes were actually the same as some that I
started to make, but wasn't sure if lines with :: would work, so I never
followed through.
In any case, it all seems to work, so thanks for your help! ($db = new
DB_mysql;$db->connect("mysql:...");)
In a partially related question, does anyone know how it would be possible
to share a single database connection (class) among a number of other
classes without having to pass it as a parameter? (I think Java has
something along this line - a connection pool or something).
seth
-----Original Message-----
From: Hagenbuch, Chuck [mailto:chagenbu@wso.williams.edu]
Sent: Saturday, June 24, 2000 11:39 AM
To: Seth Fitzsimmons
Cc: php-pear@lists.php.net
Subject: Re: [PHP-PEAR] PEAR Status
Quoting Seth Fitzsimmons <seth@egrad2000.com>:
> Is PEAR ready for primetime use? (In CVS versions anyway - I tried to use
> it in 4.0.0 and found that a couple of keywords have yet to be
implemented.)
> I'd really like to use the DB modules as a replacement for phplib (as it's
> part of the base distribution).
I haven't seen much activity around it recently. Horde (http://horde.org/)
is
planning on using the database modules; to that end, I committed some fixes
to
php4 cvs that lets the pear stuff run, at least for basic operations. I have
a
test script that gets results from a mysql database which works, at least -
I
haven't done extensive testing yet.
If you can grab those files out of cvs, I'd be very interested in how they
work
for you, and I'm perfectly willing to stomp out any remaining bugs.
Also, there are a few people working on javadoc-like parsers, which PEAR has
(sort-of?) adopted as a coding standard for inline documentation. We're also
busy adapting all the stuff we have in the various Horde code libraries into
PEAR-style classes, complete with inline documentation.
-chuck
--
I won't die for Fernando Poo
--
PHP Extension and Add-on Repository (PEAR) mailing list.
Documentation can be found at http://pear.php.net/doc/pear.html
To unsubscribe, e-mail: php-pear-unsubscribe@lists.php.net from the
mail address you subscribed with.