RE: [PEAR-DEV] DB_Light
| From: | lustig at acsu dot buffalo dot edu | Date: | Tue, 04 Dec 2001 19:37:04 +0000 |
| Subject: | RE: [PEAR-DEV] DB_Light | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-3374@lists.php.net to get a copy of this message | ||
Quoting Lukas Smith <smith@dybnet.de>:
> I just would prefer not to force the user to make this decision but to
> load this added functionality dynamically so the user only loads the
> code he actually uses. Unfortunately I do not know how to do this. Or
> I
> currently do not have a good idea anyways.
Well, that would defeat the purpose of loading as little code as
possible, because to give the user the choice would not only force you
to load that code, but force you to parse what they want, which would
slow things down.
> So yes the point is to load as few code as possible. But it would be
> much nicer not to force the user to make a decision about what
> features
> he may use at the point of db object creation.
Actually, what might be possible would be to create a script that
creates "custom" versions of PEAR::DB -- ie, it *always* includes
certain functions, like query(), but it also gives you the option to
"add" functionality. It would create a file and print out the code for
that version of PEAR::DB into the file, and you could create your custom
version with exactly what you need and not what you don't... and if you
ever need to add something, you can run the script again and create a
new "custom abstraction layer"...
--Jason