> > So, in case of "return new", wouldn't it make sense to remove the
> > warning as the code is 'legal'? And please, don't start a new "it's
> > just a friendly notice" flame war.
>
> It's just a notice, tune your error_reporting level accordingly.
Sorry, but that is just a stupid killer
Matthias Pigulla schrieb:
>>>So, in case of "return new", wouldn't it make sense to remove the
>>>warning as the code is 'legal'? And please, don't start a new "it's
>>>just a friendly notice" flame war.
>>
>> It's just a notice, tune your error_reporting level accordingly.
>
>
> Sorry, but
Sorry, Olli, if that kind of ignores your statements, but I would like
not to distract from the issue. IIRC, what you suggested is called
"boxing" in C# and would lead too far here.
I wanted to focus only on the "return new ..." case and only on PHP4, as
"return new" is a very special case. This p
Derick Rethans wrote:
You don't need this, as there is:
http://no.php.net/date_default_timezone_set
cool ..
now we only need to get the list of possible legal TZ's documented (or
linked from the docs) .. atleast I do not see it yet (but it might be just
me not seeing it at 5 am after coming
On Sun, 9 Oct 2005, Lukas Smith wrote:
> Derick Rethans wrote:
>
> > You don't need this, as there is:
> > http://no.php.net/date_default_timezone_set
>
> cool ..
>
> now we only need to get the list of possible legal TZ's documented (or linked
> from the docs) .. atleast I do not see it yet (b
> I started the build when I got home at 3am ;-) It's now online:
> http://www.php.net/manual/en/timezones.php, I'll check later
> today where I want to link this in exactly.
Nice work on this TZ stuff Derick.
My thanks.
Best,
Mike Robinson
--
PHP Internals - PHP Runtime Development Mailing
I'm not sure if all the patches are commited as for now, but it still
doesn't work for me. First, IDT setting still returns unknown timezone,
second, now PHP crashes in:
0x08095bcd in timelib_tzinfo_dtor (tz=0x0) at php5/ext/date/lib/timelib.c:107
107 TIMELIB_TIME_FREE(tz->name);
(g
Matthias Pigulla schrieb:
> Sorry, Olli, if that kind of ignores your statements, but I would like
> not to distract from the issue. IIRC, what you suggested is called
> "boxing" in C# and would lead too far here.
I knew I was going further in my comment regarding this issue. It was
never meant as
> The "return new..." is just a subset of the problem, but not
> the only one that is in wide use. For example, this is very common:
>
> function &getstuff($in)
> {
> if ($in=='ok')
> return new MyObject();
> else
> return false; // this is the common line
> }
>
> The "false" obvious
I'm not sure if all the patches are commited as for now, but it still
doesn't work for me. First, IDT setting still returns unknown timezone,
second, now PHP crashes in:
0x08095bcd in timelib_tzinfo_dtor (tz=0x0) at
php5/ext/date/lib/timelib.c:107
107 TIMELIB_TIME_FREE(tz->name);
Hm, thinking a little more about this one:
> > function &getstuff($in)
> > {
> > if ($in=='ok')
> > return new MyObject();
> > else
> > return false; // this is the common line
> > }
"return false" (or null) is trying to return a reference to a literal,
which is (of course) questiona
Matthias Pigulla schrieb:
> [...] The "return new" issue has the interesting side
> effect that notices disappear depending on the constructor's
> implementation details.
Yes. If the language insists on getting on my nerves, well, then it
should at least be consistent in doing do ;-)
> Many peopl
I have been advised by Steph that I should apply for a cvs account. I have been
helping out with php-gtk windows builds and adapting the scintilla editing
component to php-gtk2.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
13 matches
Mail list logo
