Likely Delphi yeah :)
Ron
"Marcus Boerger" <[EMAIL PROTECTED]> schreef in bericht
news:[EMAIL PROTECTED]
> Hello Ron,
>
> hehe, maybe confused with delphi or borlands c++ additons? Speaking of
> which before we add 'readonly' we should go for full property support but
> on the other hand that m
Derick Rethans wrote:
On Sun, 14 May 2006, Marcus Boerger wrote:
That said i am about to not remove E_STRICT from E_ALL and MFH the php
6.0 to item just now.
See: http://oss.backendmedia.com/PhP60 (add E_STRICT to E_ALL DONE (dmitry))
Since this is for the benefit of the users to prevent issu
On Sun, 14 May 2006, Marcus Boerger wrote:
> That said i am about to not remove E_STRICT from E_ALL and MFH the php
> 6.0 to item just now.
> See: http://oss.backendmedia.com/PhP60 (add E_STRICT to E_ALL DONE (dmitry))
>
> Since this is for the benefit of the users to prevent issues with
> chang
Marcus,
FWIW I'm with you (unusually) over E_STRICT. Why would anyone have E_ALL
switched on anywhere but a dev box? - and when there is the option to switch
on E_ALL without E_STRICT, it makes it much easier to miss useful
information about the direction PHP is going in.
Pierre: the bigges
Wez Furlong wrote:
> Probably the biggest problem is that it requires C++.
> We mentioned to you that C++ was something we avoided in PHP because
> it tends to create more problems than it's worth, particularly so in
> something that is part of the core distribution.
I must have missed that. Altho
On Sun, 14 May 2006 20:59:03 +0200
[EMAIL PROTECTED] (Marcus Boerger) wrote:
> Now the idea of E_STRICT is that core developers can inform users
> about changes in upcoming versions of php as early as possible. So
> developers should have E_ALL including E_STRICT enabled during
> development so th
On 5/14/06, Marcus Boerger <[EMAIL PROTECTED]> wrote:
Hello Wez,
and i thought i was finished with this :-)
This is the first I've heard of this, so my apologies if I should have
chimed in sooner.
Well yeah you could do things like:
[EMAIL PROTECTED] /usr/src/PHP_5_2 $ php -r "include
'd
Probably the biggest problem is that it requires C++.
We mentioned to you that C++ was something we avoided in PHP because
it tends to create more problems than it's worth, particularly so in
something that is part of the core distribution.
Can you write it in C instead?
--Wez.
On 5/12/06, Bran
Hello Wez,
and i thought i was finished with this :-)
Well yeah you could do things like:
[EMAIL PROTECTED] /usr/src/PHP_5_2 $ php -r "include
'data:;base64,PD9waHAgZWNobyAiSGVsbG8gd29ybGQKIjsgPz4=';"
make: `sapi/cli/php' is up to date.
Hello world
Hey you have a strange sender identificatio
On 5/11/06, Ralph Schindler <[EMAIL PROTECTED]> wrote:
> possible to determine the context of a T_TRY token, but nonetheless,
> it's bad practice to have functions named the same as reserved words
Thats a matter of opinion. I think its bad practice to think up a
method name that is less conci
Hello internals,
sorry the patch got lost somehow, here it is :-)
regards
marcus
Sunday, May 14, 2006, 10:12:12 PM, you wrote:
> Hello guys,
> after some incantations i came to the attached improved patch that
> allows to give properties any visibility plus mark them as public
> readable.
Hello guys,
after some incantations i came to the attached improved patch that
allows to give properties any visibility plus mark them as public
readable. The patch also implements the PHP 6.0 todo item 'readonly
for overloaded objects'.
The code now looks like:
x);
?>
Note, that this adheres
Hello internals,
from my point of view this file should contain stuff that affects any
behavior and might lead to problems. Basically anything developers should be
aware of. The NEWS file on the other hand also contains bug fix lists and
added stuff. My idea further more is to copy the behavior
Hello internals,
by accident i added both E_STRICT and E_RECOVERABLE_ERROR to E_ALL
while MFHing new features as discussed beforehand while decision was
only to MFH E_RECOVERABLE_ERROR and not to put E_STRICT into E_ALL.
See: http://oss.backendmedia.com/PhP52
Now the idea of E_STRICT is that core
Hello Jason,
Sunday, May 14, 2006, 4:34:03 AM, you wrote:
> Hello Marcus,
> class x
> {
> public readonly $xyz;
> protected readonly $abc;
> }
> Definitions:
> - public readonly- outside class can only read, not write.
> - protected readonly - subclass can only read, n
15 matches
Mail list logo
