Andi,
On 1/21/06, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> Do we have a precedent for bundling LGPL? I didn't realize we'd
> actually be bundling the code. I thought we'd rely on the library to
> be on the system. Subtle difference I know but it can be viewed as
> being part of the PHP package wh
On 1/21/06, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> At 06:15 PM 1/20/2006, Rasmus Lerdorf wrote:
> >I am all for the filter extension as well obviously, but I agree
> >there is a bit of cleanup needed and I have a bunch of things I'd
> >like to see in it, but none of them necessarily block adding
At 06:15 PM 1/20/2006, Rasmus Lerdorf wrote:
I am all for the filter extension as well obviously, but I agree
there is a bit of cleanup needed and I have a bunch of things I'd
like to see in it, but none of them necessarily block adding it.
Not sure about the functionality, and I agree some of
At 06:01 PM 1/20/2006, Rasmus Lerdorf wrote:
Andi Gutmans wrote:
Yeah, but the main problem with this kind of stuff is when you
start mapping classes and even references. I think it requires some
additional pluming to be really useful for writing robust
JavaScript<-->PHP connectivity so that i
On Fri, 20 Jan 2006 17:33:42 -0800
[EMAIL PROTECTED] (Andi Gutmans) wrote:
> Do we have a precedent for bundling LGPL? I didn't realize we'd
> actually be bundling the code. I thought we'd rely on the library to
> be on the system. Subtle difference I know but it can be viewed as
> being part o
I am all for the filter extension as well obviously, but I agree there
is a bit of cleanup needed and I have a bunch of things I'd like to see
in it, but none of them necessarily block adding it.
As far as promising it for 5.1.0? I don't recall that being the case.
It wasn't ready when we rol
Andi Gutmans wrote:
Yeah, but the main problem with this kind of stuff is when you start
mapping classes and even references. I think it requires some additional
pluming to be really useful for writing robust JavaScript<-->PHP
connectivity so that it's flexible enough for all those PHP packages
Do we have a precedent for bundling LGPL? I didn't realize we'd
actually be bundling the code. I thought we'd rely on the library to
be on the system. Subtle difference I know but it can be viewed as
being part of the PHP package which in some RMS views might end up being viral.
Omar, can you
At 05:17 PM 1/20/2006, Omar Kilani wrote:
Rasmus, Marcus,
Friday, January 20, 2006, 8:31:58 PM, you wrote:
pecl/json is a rather simple extension with no external deps (it
bundles the small library it uses). The JSON format is stable
with no real possibility of changing basically by definit
On 1/21/06, Omar Kilani <[EMAIL PROTECTED]> wrote:
> I've modified the license back to the PHP license in cvs.
>
> The reason I switched to the LGPL in the first place is so that Debian
> would allow inclusion of the package. :)
The debian (and other distros) problem is solved by the PHP License
Rasmus, Marcus,
Friday, January 20, 2006, 8:31:58 PM, you wrote:
pecl/json is a rather simple extension with no external deps (it bundles
the small library it uses). The JSON format is stable with no real
possibility of changing basically by definition, and I see its use
exploding this year
Yeah, but the main problem with this kind of stuff is when you start
mapping classes and even references. I think it requires some
additional pluming to be really useful for writing robust
JavaScript<-->PHP connectivity so that it's flexible enough for all
those PHP packages to start using it.
I've always been in favor of having ext/filter in standard PHP. It's
time we added some security supporting features.
Only thing I'd like to do before that is improve the naming
conventions a bit. Functions filter_* and I think the constant naming
like FL_* and FS_* is a bit confusing. But those
I'm not against this extension. I'd just very much like to
see the filter extension finally in core as was promised
for 5.1.0 once upon the time..IIRC.
--Jani
On Fri, 20 Jan 2006, Andi Gutmans wrote:
JSON is actually useful for real-world apps and not only for
buzzword-comp
On 1/21/06, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> JSON is actually useful for real-world apps and not only for
> buzzword-compliance :)
A release could help to get a wider audience. It is not yet available
for common users under pecl.php.net.
--Pierre
--
PHP Internals - PHP Runtime Developme
On Fri, 20 Jan 2006, Andi Gutmans wrote:
> JSON is actually useful for real-world apps and not only for
> buzzword-compliance :)
But so is pecl/filter ...
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
JSON is actually useful for real-world apps and not only for
buzzword-compliance :)
At 02:02 PM 1/20/2006, Jani Taskinen wrote:
yet-another-must-have-because-it-is-sexy-and-buzzword-compliant
extension..
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http:/
It's pretty simple.
string json_encode(mixed whatever)
mixed json_decode(string encoded_whatever)
It's just a serializer.
-Rasmus
Andi Gutmans wrote:
Hey,
I think having a JSON extension for PHP is a good idea. We have written
our own implementation in PHP for framework but could defini
What about pecl/filter ?!
I find that much more important and useful than any
yet-another-must-have-because-it-is-sexy-and-buzzword-compliant extension..
--Jani
On Fri, 20 Jan 2006, Andi Gutmans wrote:
Hey,
I think having a JSON extension for PHP is a good idea. We have wri
Hey,
I think having a JSON extension for PHP is a good idea. We have
written our own implementation in PHP for framework but could
definitely benefit from a C extension down the road if it gets widely adopted.
My only concern is that this is a very new extension and I haven't
seen any docs y
As long as the extension is licensed under the PHP License, I don't see
a problem with including in PHP 6.
Ilia
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello Rasmus,
Friday, January 20, 2006, 8:31:58 PM, you wrote:
> pecl/json is a rather simple extension with no external deps (it bundles
> the small library it uses). The JSON format is stable with no real
> possibility of changing basically by definition, and I see its use
> exploding this
pecl/json is a rather simple extension with no external deps (it bundles
the small library it uses). The JSON format is stable with no real
possibility of changing basically by definition, and I see its use
exploding this year. There is also talk to a JSON Request object being
added to browse
Guys, please take this offlist. Undefined means undefined. There's no
assumed way of it working.
Andi
At 07:14 AM 1/20/2006, Carl P. Corliss wrote:
Jon Dowland wrote:
On Thu, Jan 19, 2006 at 06:41:17PM +0200, Marco Kaiser wrote:
Today during a session i had a strange "magic" feature found i
i'm not sure if this is the right place for feature requests... apologies
if it isn't...
there doesn't seem to be a feasible way to add text string comments to
image files generated by PHP.
it would be great if there were an argument for a 'string comment' in
imagepng(), imagejpeg(), imagegi
Jon Dowland wrote:
On Thu, Jan 19, 2006 at 06:41:17PM +0200, Marco Kaiser wrote:
Today during a session i had a strange "magic" feature found in php.
this works perfect as expected. it returns 22.
Odd, I expected 21:
echo (11 + 10)
a = a + 1
nope - discounting the 'unde
On Thu, Jan 19, 2006 at 06:41:17PM +0200, Marco Kaiser wrote:
> Today during a session i had a strange "magic" feature found in php.
>
> $a = 10;
> echo ++$a + $a++;
> ?>
>
> this works perfect as expected. it returns 22.
Odd, I expected 21:
echo (11 + 10)
a = a + 1
--
Jon Dow
27 matches
Mail list logo
