As you're using this in the context of the object, I don't think it's
too confusing. I actually find the latter more confusing and think
it's best to stick to what we have today.
Andi
At 12:08 AM 1/23/2006, Lukas Smith wrote:
Andi Gutmans wrote:
Yes, this was by design. Via class it should be
Omar Kilani wrote:
All,
On 1/22/06, Derick Rethans <[EMAIL PROTECTED]> wrote:
On Sat, 21 Jan 2006, Andi Gutmans wrote:
Yep, I think you're right.
It's always easier when it's not in the core because then it's clear that
you're just linking. So I think if as long as we make sure not to touch t
All,
On 1/22/06, Derick Rethans <[EMAIL PROTECTED]> wrote:
> On Sat, 21 Jan 2006, Andi Gutmans wrote:
>
> > Yep, I think you're right.
> > It's always easier when it's not in the core because then it's clear that
> > you're just linking. So I think if as long as we make sure not to touch the
> > l
Marcus Boerger schrieb:
> helly Tue Jan 24 20:19:49 2006 UTC
>
> Added files:
> /php-src/ext/reflection/tests 007.phpt
>
> Modified files:
> /php-src/ext/reflection php_reflection.c
> Log:
> - Implemented #36141 Add ReflectionClass::n
Wez Furlong wrote:
> As Gareth points out, an RRDTool extension is a no-go for the PHP
> project due to a licensing conflict.
>
> The best I can suggest is hosting your project on sourceforge.net.
... digging up an old thread, here..
I happened up the rrdtool site, today, and saw this:
http://peo
On Mon, Jan 23, 2006 at 06:00:24PM +0100, Pierre wrote:
>
> A "working" strip_tags, something like strip_tags_ex :)
Ah. My brain was still on the JSON part of this thread and was befuttled
by Rasmus talking about tags and attributes in relation to JSON.
Pardon,
--Dan
--
T H E A N A L Y S
> > JSON in general looks far better suited to the PHP->js layer..
>
> Yup, until browsers start sending JSON requests natively, I don't see
> much js->PHP usage either. PHP->js is the much more common
> use case at this point.
We are working on better browser support for JSON. We are develo
Hello all, I hope this is the right place to write about this. I've been
trying now for quite some time to integrate php into my non-apache server
(completely c++ written by me).
Sounds like you want to use sapi/embed (or write a SAPI implementation of
your own which is notably more involved).
I'm lead developer of PEAR package "Services_OpenSearch".
http://pear.php.net/pepr/pepr-proposal-show.php?id=336
Recently finish voting and accepted my package. So before first release, I nedd
CVS account for managing my package.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubs
Hello all, I hope this is the right place to write about this. I've been
trying now for quite some time to integrate php into my non-apache server
(completely c++ written by me). Right now I have it working partially using
the CLI. My application generates a shell script when a .php page is
request
Zitat von Derick Rethans <[EMAIL PROTECTED]>:
Hello!
For some reason all of our code in all repositories in CVS have a tag
"RELEASE_1_0_4". Seems to have happened on the 18th, according to the
timestamp in the ChangeLog's history:
http://cvs.php.net/viewcvs.cgi/php-src/ChangeLog?view=log
If yo
11 matches
Mail list logo
