+1 for removal.
Scott MacVicar [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hi everyone,
We've discussed this a few times in the past and it's time to make a
final decision about its removal.
I think most people have agreed that this is the way forward but no one
has
Quoting Lokrain [EMAIL PROTECTED]:
Hi,
The company I work for has as a rule to update it's projects to the latest
php. This starts usually one month before the official release.
Can you tell me when will php 5.3 be released? Of course not the exact date
but something around it :) Like month?
Hi Christian,
Am Sonntag, den 04.05.2008, 12:14 +0200 schrieb Christian Hoffmann:
[...]
as a distribution we usually aim at using system libraries instead of
bundled ones, both for security and maintainance reasons.
PHP bundles liboniguruma (ext/mbstring/oniguruma) and currently does not
2008/4/23 Piotr Czachur [EMAIL PROTECTED]:
Hello!
I use PHPUnit for unit testing of my application (but this issue is
independent of PHPUnit). Tests are run from command line so it's not
way (that I can imagine) to simulate file upload, because app code
uses is_uploaded_file() to check
Hi Rasmus,
Sorry about the patch format. :-/ It's been updated to correct that, as
well as fix a test failure that Felipe mentioned. And as Felipe said, the
invalid opcode is because the patch doesn't include the zend_vm_execute.h
changes, and zend_vm_gen.php needs to be run first. I also
Hi Felipe, all,
The patches have been updated to fix the failing nowdoc_015.phpt test.
http://realplain.com/php/string_optimizations.diff
http://realplain.com/php/string_optimizations_5_3.diff
The problem was that after removing the ST_START_NOWDOC stuff, the
NOWDOC_CHARS pattern wasn't
Hello John,
the main reason really is storage. If you allow storage in interfaces
then you get multiple inheritance with its virtual inheritance (diamond
style inheritance) issue. That however onlly applies to plain attributes
and not properties which are usually understood as attributes that
Marcus Boerger wrote:
A much shorter thing to do might be:
interface Coord {
abstract $coord;
}
Something like that is exactly what I was looking for in my original
question. I don't want to specify implementation details, I just want to
ensure the property exists on the classes that
Hi Marcus,
I think this is really specifying implementation details in an
interface:
interface Coordinate {
public $coord = __get = getCoord, __set = setCoord,
__isset = hasCoord, __unset = delCoord;
public getCoord();
public setCoord($val);
public hasCoord();
public
Hi Marcus, et al.,
Am Dienstag, den 06.05.2008, 09:09 -0700 schrieb Jeff Moore:
[...]
I think this is really specifying implementation details in an
interface:
I agree.
[...]
This looks to me like the best way to handle this in interfaces:
interface Coord {
abstract $coord;
}
I
On Tue, May 6, 2008 at 1:21 PM, Lars Strojny [EMAIL PROTECTED] wrote:
I think this is too unspecific. At least the visibility, setter and/or
getter and type-hint (assuming we will have type hints) should be
defined. Otherwise defining properties in interfaces become useless as
it does not
Hi Matt,
about optimization..., do you have any test for comparison? Why, in my
crazy test (http://rafb.net/p/ZzQQQP97.html), the actual code is more
faster than your patch.
real0m1.156s
vs
real0m1.368s
(using time command)
I'm just curious, i'm not against your patch.
Thanks.
Em
Hello Lars,
Tuesday, May 6, 2008, 9:21:12 PM, you wrote:
Hi Marcus, et al.,
Am Dienstag, den 06.05.2008, 09:09 -0700 schrieb Jeff Moore:
[...]
I think this is really specifying implementation details in an
interface:
I agree.
[...]
This looks to me like the best way to handle this
Hi Marcus!
Am Dienstag, den 06.05.2008, 21:45 +0200 schrieb Marcus Boerger:
[...]
All fine with me. However we *would* need to specify which function is
getter, setter, isset or unset.
[...]
public $property {
string public function __get() {
return $this-_property;
}
string
Marcus,
I think the idea of supporting properties via getters/setters is a fine
idea (just like Java, Delphi etc). Many of us simulate this behaviour
with __get()/__set(), and it would be nice to formalise it a little.
However I don't quite understand the multiple inheritance argument - I
Hi All,
Lars Strojny schrieb:
Hi Marcus!
Am Dienstag, den 06.05.2008, 21:45 +0200 schrieb Marcus Boerger:
[...]
All fine with me. However we *would* need to specify which
function is getter, setter, isset or unset.
[...]
public $property { string public function __get() { return
16 matches
Mail list logo
