>From the user point of view it might seem that 5.x "string" and 6.x
"unicode" are all strings, whatever you call them. Still, I am sure
there _is_ a background for the decision to distinguish between
"string" and "unicode".
2 марта 2010 г. 1:27 пользователь Antony Dovgal написал:
> On 03/01/2010
On 03/01/2010 11:35 PM, Stan Vassilev wrote:
>
> Hi,
>
> The gettype() documentation warns people that the returned string is "subject
> to change".
> Why is there a function that's subject to change in the API?
Because life is complicated.
Because gettype("test") returns "string" in 5.x and
On Mon, Mar 1, 2010 at 23:19, Hannes Magnusson
wrote:
> Hi all
>
>
> Now that Google will start accepting mentoring organization
> applications around this weekend we need to start brainstorming for
> ideas.
>
> Philip has already made some cleanups on the wiki and reorganized some
A link to the
On 01.03.2010 21:35, Stan Vassilev wrote:
> The gettype() documentation warns people that the returned string is "subject
> to change". Why is there a function that's subject to change in the API?
Probably because of the unicode stuff, might suddenly return "unicode"
(still true? don't know) or "
Hi all
Now that Google will start accepting mentoring organization
applications around this weekend we need to start brainstorming for
ideas.
Philip has already made some cleanups on the wiki and reorganized some
things to be slightly more general, so feel free to propose ideas that
don't take "
In my opinion this is consistent with the fact that PHP has no
block-scoped variables. The situation is similar with the one in JavaScript.
In JavaScript the problem has been solved by Mozilla with so-called let
definitions[1], which are block-scoped.
1:
https://developer.mozilla.org/en/New_
Hi,
The gettype() documentation warns people that the returned string is "subject
to change". Why is there a function that's subject to change in the API?
And just to clarify: I agree is_*() is better if we test for a certain type (as
the note says). However, the use scenario for gettype() is
Java has a transient keyword to skip serialising a property and I have
a patch against 5.3 on http://whisky.macvicar.net/patches/
It might make it in to 5.4/6/next once I get some more free time.
Scott
On 1 Mar 2010, at 02:10, Jordi Boggiano wrote:
On 01.03.2010 10:31, Tjerk Meesters wrote
Etienne Kneuss wrote:
Hello,
On Mon, Mar 1, 2010 at 1:33 PM, mathieu.suen wrote:
Hi,
I am proposing a comparison between PHP closure with lisp one.
First thing to compare is how scope are capture:
Suppose I want to create a function that add.
The common idiom to do it in lisp is:
(defun
Hello,
On Mon, Mar 1, 2010 at 1:33 PM, mathieu.suen wrote:
> Hi,
>
> I am proposing a comparison between PHP closure with lisp one.
>
> First thing to compare is how scope are capture:
> Suppose I want to create a function that add.
> The common idiom to do it in lisp is:
>
> (defun adder (x) #'(
Hi,
I am proposing a comparison between PHP closure with lisp one.
First thing to compare is how scope are capture:
Suppose I want to create a function that add.
The common idiom to do it in lisp is:
(defun adder (x) #'(lambda (y) (+ x y)))
Then if I want the add3 method you can do:
(setf (sy
On 01.03.2010 10:31, Tjerk Meesters wrote:
> If visibility is an issue why not just use json_enode/decode for this
> case then?it doesn't seem like a typical enough problem to be solved
> low-level and json seems fast enough for the job ;-)
Honestly I personally don't care, it won't happen to me a
Hi,
If visibility is an issue why not just use json_enode/decode for this
case then?it doesn't seem like a typical enough problem to be solved
low-level and json seems fast enough for the job ;-)
Hi,
I don't know whether it should be fixed or not, but it definitely shouldn't
have received
PHP 6 Bug Database summary - http://bugs.php.net/
Num Status Summary (110 total -- which includes 47 feature requests)
===[Apache related]===
47061 Open User not logged under Apache
===[
Hi,
If visibility is an issue why not just use json_enode/decode for this
case then?it doesn't seem like a typical enough problem to be solved
low-level and json seems fast enough for the job ;-)
On 01-Mar-2010, at 4:00, Jordi Boggiano wrote:
On Sun, Feb 28, 2010 at 8:03 PM, Herman Radtk
15 matches
Mail list logo
