I've wanted to suggest for a while that there be an option to annotate the
API docs on Zend's site. There have been a few things ive discovered in the
process of extension development that could benefit fellow travelers, but as
of now there seems not to be a process (that im aware of) to
i meant to post the following link a while back, but i lost track of it
http://users.footprints.net/~kaz/kazlib_doc/docs.html
look near the bottom.
i havent tried this personally, but he seems to have a portable (Ansi C)
exception handling mechanism which appears well though out and
then thread safe, or is TSRMLS_FETCH() (or TSRMLS_C etc) needed in
each function needing serialized access to TLS data ?
lo-tek
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list
My concern is really with the globals and not the functions, so if two
threads cant simultaneously step on the same copy of globals referenced by a
tsrm resource id, then that solves my problem.
you then pass to bar). So thread safety should *not* be affected.
But AFAIK TSRM* do NOT force
Jeroen,
then i have one more question. The real problem im trying to solve is
the ability to have multiple threads (different requests) access a resource
which may be persistent.
imagine, for instance, that i have a persistent database connection which
matches the login criteria (username,
i've looked at the latest Zend CVS and like what i see with regards to
exceptions, and i'd like to make a suggestion.
in other languages (c++, delphi and Java for sure), you can specify the type
of exception you are interested in in the catch block. short of this, the
programmer would have to
at 12:03:44PM -0400, lo-tek wrote:
A new OOP database abstraction layer (in C) is in the works.
Should be ready
in 2 or so months...
how is that going to be different from PEARs or the dbx one?
tc
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail
