#x27;s what is required to get this to pass.
>
> S
>
>
While I would have been happy with the short array syntax proposed
earlier, I do have to say that Sean's points make a lot of sense to me
and I am strongly inclined to agree with him.
I can't really see any harm in thi
personal preference. I'm okay with either
> flag, to be honest.
>
> --
> Matthew Weier O'Phinney
> Project Lead| matt...@zend.com
> Zend Framework | http://framework.zend.com/
> PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc
&
ement array, and it must be
> > for the first element object/string and for the second string only. (just
> > like our zend_is_callable() check and opcodes related to init call)
> >
> > Any thoughts?
> >
> > [1] - http://bugs.php.net/bug.php?id=47160
> > [2
On 6/4/2011 8:55 PM, Philip Olson wrote:
In parallel I'd also see if there are any key extensions which we think are
mainstream, stable and well maintained enough to be included. For example, http
comes to mind.
Enable pecl_http by default (or, always), and bundle APC.
Regards,
Philip
APC, +
On 6/3/2011 8:27 AM, Dennis Haarbrink wrote:
As soon as I have my requested write permission in the rfc namespace i will
update it.
--
Dennis Haarbrink
2011/6/3 Pierrick Charron
Hi,
The RFC was supposed to be a draft (i didn't really added it in the good
section) and was written more to int
n.
Bitte, reg dich ab.
- M.
On 6/2/2011 11:34 AM, Reindl Harald wrote:
Am 02.06.2011 17:01, schrieb Peter Lind:
On 2 June 2011 16:50, Reindl Harald wrote:
Am 02.06.2011 16:24, schrieb Marcel Esser:
I am not convinced that making this an error is a good idea.
If I receive a $_GET/$_POST valu
16:54, schrieb Marcel Esser:
You don't need a form to receive bad user input.
Also, I am not really inclined to write $v = isset($_POST['x']) ?
(is_array($_POST['x']) ? 'something else that
makes more sense' : $_POST['x'] ) : null; just to avoid catching a
6/2/2011 10:50 AM, Reindl Harald wrote:
Am 02.06.2011 16:24, schrieb Marcel Esser:
I am not convinced that making this an error is a good idea.
If I receive a $_GET/$_POST value that I expect to be a string value, but I
actually received an array, this would
mean I need to now explicitly
I am not convinced that making this an error is a good idea.
If I receive a $_GET/$_POST value that I expect to be a string value,
but I actually received an array, this would mean I need to now
explicitly check for it, since it will stop the runtime otherwise. Example:
http://home.sweet.home
<3 yes please.
Sent from my iBrain, powered by Panda.
On Jun 2, 2011, at 6:19 AM, "Patrick ALLAERT" wrote:
> Hi,
>
> I would like to introduce an E_NOTICE when an array is silently
> converted to a string.
> This isn't very useful as it constantly produces the following string:
> "Array" and i
they are always in quotation marks, so it
shouldn't really be such a terrible issue to delimit as such. I am not
certain about that, but, again, json_decode seems to manage.
- M.
--
Marcel Esser
Vice President of Engineering, CROSCON
+1 (202) 470-6090
marcel.es...@croscon.com
Before print
se of JSON or JSON-superset notations.
- M.
--
Marcel Esser
Vice President of Engineering, CROSCON
+1 (202) 470-6090
marcel.es...@croscon.com
Before printing this e-mail, please consider the rainforest.
On 6/1/11 6:17 PM, "Michael Shadle" wrote:
>On Wed, Jun 1, 2011 at 3:09
really
easy to learn.
It really just makes things easier in the long run. X APIs are adopting
JSON as a query format, hence, if we can support JSON fully, the learning
curve for expressing these queries gets sliced and diced. And as Sean
said, a lot less error prone.
Cheers,
M.
--
Marcel Esser
Vi
My kneejerk reaction to this, as no one particularly important, is to
not allow mixing those syntaxes.
I looked at the RFC a minute ago, and I read a reference to a parallel
solution to this being named parameters. Which, I think, is not
accurate. The problem with the array() notation is defin
interchange
>format (the most efficient one) but not the easiest to read for
>configuration or manually defining anything.
>
>I see nothing wrong with the initial example. Has worked well for years.
>:)
>
>
>On May 31, 2011, at 3:43 PM, Marcel Esser
>wrote:
>
e. I don't know anyone that needs the
ability to support full JSON notation in PHP, but there are entirely too many
deeply nested array() declarations with lots of tabs in our lives, especially
when we start working with things like JSON and/or Mongo or xyz.
That's all I wanted to say to this.
Cheers,
M.
--
Marcel Esser
Vice President of Engineering, CROSCON
+1 (202) 470-6090
marcel.es...@croscon.com
Before printing this e-mail, please consider the rainforest.
Using ::: as a namespace seperator would be great.
---
Marcel Esser, Technical Lead
Croscon, LLC
http://www.croscon.com
---
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
17 matches
Mail list logo
