Hello Jeff,
there is no way in implementing multi-whatever observer and subjects
typesafe. If you want that you'd end up calling them MySubjectWhatever,
MySubjectWhatnot, MySubjectWhatelse, ... and MyObserverWhatever, ...
The other thing you mentioned, sending information along, is not necessary
Jeff Moore schrieb:
> The problem with the Observer interface is that any class implementing
> it is only capable of receiving one kind of notification (update) and
> there is no capability to send any additional information.
>
> The problem with the Subject interface is that it can also only supp
Would it be possible to remove the Subject and Observer interfaces or
at least delay them until a later release?
The problem with the Observer interface is that any class implementing
it is only capable of receiving one kind of notification (update) and
there is no capability to send any addit
On Mon, 12 Sep 2005, Andi Gutmans wrote:
> Well in all the years I've rolled releases I have never used RCn-dev. Seems
> like this was something only applied to the 4.3 branch.
And now to the 5.1 one as well :)
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
Not coming with a solution, but I believe this would be a bad idea. I
do think some people will be using IS_UNICODE strings when
unicode_semantics=off, mainly for existing applications. They may
want to serialize Unicode strings even though their classes are
IS_STRING. It might make sense to ra
Well in all the years I've rolled releases I have never used RCn-dev.
Seems like this was something only applied to the 4.3 branch.
I'm not opposed to changing that and I'll be happy to do so, but it
would probably make sense to have a more robust comparison,
especially if it's something like "i
Hey Pierre,
Mini releases are not only for security fixes. We also do bug fixes,
and sometimes even minor functionality (like a new function) which
has very low risk of breaking anything. I don't think 5.0.5 is
different from that.
I do think we could probably be better at communicating these
Hi Rasmus,
You start a new thread for my question, maybe you will get more
answers or at least better ones.
If it is a reference or not, I do not care, it should not "act"
differently. Understand that a quiet code in 5.0.4 must be quiet in
5.0.5.
If we add notices in 5.1.0 and then make them fa
On Mon, 12 Sep 2005, Zeev Suraski wrote:
> I don't really agree that it's out of whack, since you are passing a piece of
> data by reference, which is an undefined behavior. I agree that it would have
> been nice if we could allow for this and only complain if the data is written
> to in the func
At 10:57 12/09/2005, Rasmus Lerdorf wrote:
Guys, could we take a look at making the ref to temp var fix a bit
narrower? Currently we try to catch it at call-time. This means that
something like:
current(explode(' ','a b'))
as per bug #34468 doesn't work. Now, I think there is a secondary b
On 9/12/05, Zeev Suraski <[EMAIL PROTECTED]> wrote:
> I don't think you're going to get a very good answer here. It boils down
> to what you already know - it's a bug which results in corruption, and
> that's the only way to fix it. The common decision was that it's more
> important to fix this
At 01:54 12/09/2005, Pierre Joye wrote:
Hello,
Without arguing again about the """fix""" for the memory corruption
discovered earlier this summer and without anyone able to reproduce
with a medium size script, _why_ in the world one applies this fix to
the 5.0 branche?
5.0.5 was supposed to be
can someone provide a link for the PHP debug document?
I can build PHP but it crashes apache and I'd like to fix the problem.
-- Dale
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 9/12/05, Wez Furlong <[EMAIL PROTECTED]> wrote:
>http://pecl.php.net/account-request.php
> (you should ideally have use this form in the first instance :)
And so you did... that'll teach me to read my pecl mail after the
internals mail.
Ignore my comments :)
--Wez.
--
PHP Internals - PHP
Please also use this form to request a PECL account; enter the same
user name you chose already, but leave the 'need cvs account' box
unchecked:
http://pecl.php.net/account-request.php
(you should ideally have use this form in the first instance :)
For the list: Andrew implemented this himsel
I have created a PECL extension that I am so far calling "rpmfile" that has the
ability to read the header information from Red Hat Package Manager (RPM) files
and I wish to publish this code in PECL.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.
Hi All,
Seems like Hartmut Holzgraefe had fixed the same issue for 5.1 tree on
May 30th 2005.
Can I reapply the same to 5.0 tree.
Adding http://ductape.net/~kameshj/Makefile.frag to ext/sqlite/
http://ductape.net/~kameshj/sqliteconfig.m4.patch
With regards
Kamesh Jayachandran
On Mon, 12 Sep 2005
Guys, could we take a look at making the ref to temp var fix a bit
narrower? Currently we try to catch it at call-time. This means that
something like:
current(explode(' ','a b'))
as per bug #34468 doesn't work. Now, I think there is a secondary bug
here. I see no reason for current() to ta
PHP 5 Bug Database summary - http://bugs.php.net
Num Status Summary (366 total including feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
==
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (642 total including feature requests)
===[Arrays related]===
31114 Assigned foreach modify array
34277 Assigned array_filter() crashes with references and objects
20 matches
Mail list logo
