open a bug (doc bug) and add it to the TODOs, so it won't be forgotten.
2011/11/18 Ferenc Kovacs :
>
>
> 2011/11/17 Johannes Schlüter
>>
>> Just to make one thing clear: To the best of my knowledge the module
>> works with 5.4 and trunk (it's three months since I tested, but I'm not
>> aware of a
On Thu, Nov 10, 2011 at 11:08 PM, Ralph Schindler
wrote:
> Maintenance of the Phar extension (bug fixing, documentation fixes, etc)
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
I know I don't really have vote in this, but I
this patch has been applied by Stas.
On Sat, Nov 19, 2011 at 12:55 PM, Ferenc Kovacs wrote:
> On Thu, Nov 10, 2011 at 11:08 PM, Ralph Schindler
> wrote:
>
>> Maintenance of the Phar extension (bug fixing, documentation fixes, etc)
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>
On Sat, Nov 19, 2011 at 10:14 AM, Pierre Joye wrote:
> open a bug (doc bug) and add it to the TODOs, so it won't be forgotten.
>
>
done:
https://bugs.php.net/bug.php?id=60336
https://wiki.php.net/todo/php54
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
On Sat, Nov 19, 2011 at 1:12 PM, Pierre Joye wrote:
> this patch has been applied by Stas.
>
>
I see the commit, and that reminded me replying to his request.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
hi Ralph,
The procedure is to 1st send patches over, via bugs.php.net (easier to
track) and ML, after some time you will get an account :)
Thanks for your (upcoming) work!
Cheers,
On Thu, Nov 10, 2011 at 11:08 PM, Ralph Schindler
wrote:
> Maintenance of the Phar extension (bug fixing, document
Hey guys,
I don't have a dev environment on my mac here so I can't upgrade to
TRUNK to test so I'm relying on someone on the internals list to test
this.
PHP INFO
5.3.1
-- ISSUE
Simple integer work, converting it from being wrapped in a zval.type of string,
into int. Same valu
If I'm not mistaken, that is to be expected. That's because you're on
a 32 bit system, so the maximum possible int (PHP_INT_MAX) is
2147483647. Now, normally PHP could cast to a float to get the larger
number in, but you explicitly cast it to an integer, so it had to
truncate the value.
Try var_
Thanks for the response guys.
It wasn't important that I casted my value I was just being pedantic
in the first place. Removing the cast stops be from being hit with
INT_MAX and INT_SIZE.
Cheers!
Paul Dragoonis.
On Sat, Nov 19, 2011 at 1:53 PM, Anthony Ferrara wrote:
> If I'm not mistaken, that
On Sat, 19 Nov 2011 13:46:35 -, Paul Dragoonis
wrote:
[...]
CODE ---
$s = "2433078805";
var_dump($s);
var_dump((int) $s); exit;
- EXPECTED -
string(10) "2433078805" int(2433078805)
- ACTUAL -
string(10) "2433078805" int(2147483647)
Anthony has already explained
On Sat, 19 Nov 2011 01:46:09 +, Clint M Priest wrote:
> What would everyone think about multiple levels of visibility for
> getters/setters?
>
> class Sample {
>
> public $Variable {
> public get { return "Public"; } protected get { return
> "Protected"; }
>
Just throw an error if conflicting accessors are defined. In the case of
subtypes: accessors may broaden the interface, but not limit it => LSP. So it’s
fine to make a parents protected accessor public, but not the other way around.
Am 19.11.2011 um 02:46 schrieb Clint M Priest:
> What would ev
personally i think only public should be done with this method
all others should be follow the __set/__get method, since if you need
special rules, then they would be set-able by a public method
On Sat, Nov 19, 2011 at 7:45 PM, Lars Strojny wrote:
> Just throw an error if conflicting accessors
That would be a resounding no from everyone. :)
-Original Message-
From: Hannes Magnusson [mailto:hannes.magnus...@gmail.com]
Sent: Friday, November 18, 2011 8:16 PM
To: Clint M Priest
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Multiple Visibility Level Getters/Setters
On Sat, No
It seems gmail broke newlines :(
but you'll see the idea.
--
Yasuo Ohgaki
yohg...@ohgaki.net
2011/11/20 Yasuo Ohgaki :
> This is not a alternate syntax suggestion, but a currently working
> solution (well partial)
>
> ($this->r_property[$name]) return $this->$name; else
> trigger_error
This is not a alternate syntax suggestion, but a currently working
solution (well partial)
r_property[$name]) return $this->$name;else
trigger_error("Access to read protected property");}
public function __set($name, $value) { if ($this->w_property[$name])
$this->$name = $value; else
Link us to a http://gist.github.com paste please Yasou. Thanks.
On Sat, Nov 19, 2011 at 9:45 PM, Yasuo Ohgaki wrote:
> It seems gmail broke newlines :(
> but you'll see the idea.
>
> --
> Yasuo Ohgaki
> yohg...@ohgaki.net
>
>
>
> 2011/11/20 Yasuo Ohgaki :
>> This is not a alternate syntax suggest
Sure. I did.
https://gist.github.com/1379592
--
Yasuo Ohgaki
yohg...@ohgaki.net
2011/11/20 Paul Dragoonis :
> Link us to a http://gist.github.com paste please Yasou. Thanks.
>
> On Sat, Nov 19, 2011 at 9:45 PM, Yasuo Ohgaki wrote:
>> It seems gmail broke newlines :(
>> but you'll see the idea.
18 matches
Mail list logo
