Hey:
is there any change to git box recently?
I got a fail message like:
Total 5 (delta 3), reused 0 (delta 0)
remote: Shared object "libvpx.so.0" not found, required by "php"To
g...@git.php.net:php-src.git
thanks
--
Laruence Xinchen Hui
http://www.laruence.com/
--
PHP Internals
hi,
No, we won't implement that as it is already available by default on
windows. check the AutoBackupLogFiles option.
For people not using windows log system but classic files, there are
plenty of tools to do it as well.
Cheers,
On Sat, Oct 27, 2012 at 11:53 AM, Kris Craig wrote:
> On Sat, Oc
> -Original Message-
> From: Clint Priest [mailto:cpri...@zerocue.com]
> Sent: 28 October 2012 16:03
>
> So... to be explicit here, you think in this situation:
>
> class a {
>public $b {
> set($x) { $this->b = $x; }
>}
> }
>
> $o = new a();
>
> if(!isset($o->b)) {
>/*
On 10/29/2012 12:20 AM, Laruence wrote:
> Hey:
>is there any change to git box recently?
>
>I got a fail message like:
>
>Total 5 (delta 3), reused 0 (delta 0)
>remote: Shared object "libvpx.so.0" not found, required by "php"To
> g...@git.php.net:php-src.git
This is fixed now.
On Mon, Oct 29, 2012 at 9:16 PM, Rasmus Lerdorf wrote:
> On 10/29/2012 12:20 AM, Laruence wrote:
>> Hey:
>>is there any change to git box recently?
>>
>>I got a fail message like:
>>
>>Total 5 (delta 3), reused 0 (delta 0)
>>remote: Shared object "libvpx.so.0" not found, required b
Hi!
> So... to be explicit here, you think in this situation:
>
> class a {
>public $b {
> set($x) { $this->b = $x; }
>}
> }
>
> $o = new a();
>
> if(!isset($o->b)) {
>/* delete files */
> }
> echo (int)isset($o->b); /* This should return false and not emit any
> sort of war
Hi!
> Is there another class of error that would make more sense? Don't most
> people turn off E_NOTICE errors? Perhaps emit an E_STRICT?
I always run with E_NOTICE in development, that's kind of what E_NOTICE
is for :) I don't think isset() should produce any warnings/notices -
this is how it
Hi!
> If I got it right now, what Stas wants is that we introduce __getFoo
> and __setFoo methods that will be called whenever an undefined ->foo
> property is accessed and that the "normal" property accessors syntax
> is made nothing more than a fancy notation for this.
Yes, pretty much, though
On Mon, Oct 29, 2012 at 10:56 PM, Stas Malyshev wrote:
> Hi!
>
>> If I got it right now, what Stas wants is that we introduce __getFoo
>> and __setFoo methods that will be called whenever an undefined ->foo
>> property is accessed and that the "normal" property accessors syntax
>> is made nothing
Hi all,
On 27/10/12 12:49 PM, Lars Strojny wrote:
Hi,
thanks for bringing this up again. I digged even deeper into the whole issue of converting floats to strings
and my current findings are that we can’t solve that consistently as things are already fubar’ed. The reason
for that is, that in
http://wiki.php.net/rfc/uconverter
Discuss!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
hi Sara!
On Tue, Oct 30, 2012 at 2:57 AM, Sara Golemon wrote:
> http://wiki.php.net/rfc/uconverter
>
> Discuss!
Nice job!
Some comments, raw :) :
- the UCNV prefix is not necessary, we are in the UConverter class
already, I would simply use LATIN_1, or ILLEGAL for exampe.
- It is OO, we should
btw, can you add the changes to config.w32 too pls? Pretty much the
same than in .m4, so I can add it to our CI and valid the RFC patch
in a more handy manner :)
On Tue, Oct 30, 2012 at 2:57 AM, Sara Golemon wrote:
> http://wiki.php.net/rfc/uconverter
>
> Discuss!
>
> --
> PHP Internals - PHP Ru
Very nice work.
Bravo!
On 30/10/12 02:57, Sara Golemon wrote:
http://wiki.php.net/rfc/uconverter
Discuss!
--
Ivan Enderlin
Developer of Hoa
http://hoa.42/ or http://hoa-project.net/
PhD. student at DISC/Femto-ST (Vesontio) and INRIA (Cassis)
http://disc.univ-fcomte.fr/ and http://www.inria
14 matches
Mail list logo
