[binarycloud-dev] PEAR_Error and other things

[Alex B. <en...@tu...>]

Anyone have opinions on using PEAR_Error as the error class for binarycloud
r2?

"Speak now or forever hold your peace" :) I've looked over it, and am happy
with it. Unless someone comes up with some _really_good_ negative arguments,
we'll use it.

Keep in mind that we'll still use the custom error handler that logs all
errors to the DB, but I'd like to deprecate throw_error (which is in
core/base/err/error_handler.php for the curious) - it works, but it's not
groovy.

Obviously because we're using PEAR_Error, we'll need to use the base PEAR
class, which means you can get access to the entire PEAR library of classes
(and while the DB code isn't fast enough, some of the other code is quite
good). There will be a pear directory in the r2 distro core/lib/, which will
store any pear code we need in the system. The same thing might be done for
phplib, because could theoretically support phplib's DB abstraction, which
means developers with phplib apps could move into binarycloud with fairly
little pain.

I'm also going to "formally announce" (in the docs) that all of the
binarycloud base classes and distro modules will/do roughly adhere to the
PEAR standard, though I can't bring myself to enforce the
"tabs-must-be-4-spaces" rule.

---

A major (read: clear) revision of the r2 specs will be up fairly soon, as
I've worked out the final structure in my head, and just need to write it
down and finalize the list of constants.


_alex


--
alex black, ceo
en...@tu...

the turing studio, inc.
http://www.turingstudio.com

vox+510.666.0074
fax+510.666.0093