2009/9/17 Chris Trahey ctra...@csisd.org:
It seems worthwhile in a service-provider situation where you do not wish to
enforce use of $this in service consumers.
The service provider can impliment caller without modifying existing code.
Semantically, it should be considered redundant to pass
Ian Tighe wrote:
Hi. I hope this has been sent to the right place.
I am using files that are mount.cif share files. My client is a samba linux
box but acting as a client over cifs to an XP box (several in fact).
I am descending the share recursively with opendir and readdir detecting
files
Hi ,
I am using readdir with a view to selecting files for opening and reading or
just taking a stat of them. I am doing this recursively. I test the output
from readdir to see if its a file or dir or link etc and this works well.
This suddenly changes though and an item is returned by readdir
Ian Tighe `wrote:
Hi ,
I am using readdir with a view to selecting files for opening and
reading or just taking a stat of them. I am doing this recursively. I
test the output from readdir to see if its a file or dir or link etc
and this works well. This suddenly changes though and an item is
Yes readdir was an example and I am saying error reporting is not very good.
I am suggesting ( requesting a feature ) that all I/O functions should
return better information so we can detect outcomes of I/O - whichever
function is used, whatever file system, whatever circumstance.
-
On 15.09.2009, at 09:04, Lester Caine wrote:
I have no doubt that PDO works fine for many people, but since the
limited target that it had was for data abstraction IS this actually
achieved currently? Which drivers ARE fully functional, and what
outstanding bugs remain on each?
The list
Isn't this exactly what the backtrace is for?
That's fair... but there are ate least two things undesireable about using
the backtrace:
1. Performance - we can get the caller less work
2. using it is current-implimentation specific (i.e. developer needs to
know the format of the array returned)
Chris Trahey schrieb:
using it is current-implimentation specific (i.e. developer needs to
know the format of the array returned)
And adding another language feature is not something the developer needs
to know?
--
Sebastian BergmannCo-Founder and Principal Consultant
And adding another language feature is not something the developer needs
to know?
Once implimented, it would be obvious that a constant like caller always
means caller.
It is not obvious that the caller object is located in the object key of
the second element of the array returned by
Sebastian Bergmann wrote:
Chris Trahey schrieb:
using it is current-implimentation specific (i.e. developer needs to
know the format of the array returned)
And adding another language feature is not something the developer needs
to know?
I think the concern is the overhead of capturing
On Wed, Sep 16, 2009 at 1:59 PM, Chris Trahey ctra...@csisd.org wrote:
(Please direct me elsewhere if necessary, this is a feature request)
It would be handy to allow a method to behave differently based on who is
calling it.
the function I am looking for would essentially do this:
.. snip
For each use case, there are going to be ways to acheive results without
new functionality. I think this feature doesn't make the impossible
possible, it gives developers a consistent interface to access an object
that is potentially very relevant, and perhaps not desired to be necessary
in the
On Thu, Sep 17, 2009 at 10:05 AM, Chris Trahey ctra...@csisd.org wrote:
For each use case, there are going to be ways to acheive results without
new functionality. I think this feature doesn't make the impossible
possible, it gives developers a consistent interface to access an object
that is
Lukas Kahwe Smith wrote:
Anyways it all boils down to having developers care. It mostly works for
MySQL and SQLite I guess. PostgreSQL has seem some love recently. IBM
seems to not care anymore. Oracle certainly doesnt. Microsoft never did.
A really bad situation for such a core technology.
The PHP development team would like to announce the immediate
availability of PHP 5.2.11. This release focuses on improving the
stability of the PHP 5.2.x branch with over 75 bug fixes, some of
which are security related. All users of PHP 5.2 are encouraged to
upgrade to this release.
15 matches
Mail list logo
