On Tue, 12 Oct 2004, Sascha Schumann wrote:
> On Mon, 11 Oct 2004, Andi Gutmans wrote:
>
> > I think you are right. The only problem I can see is that people added more
> > than one header with a header() call and it actually having worked under some
> > SAPIs. My guess is that this has happened q
Andi Gutmans wrote:
What do you expect to happen?
BTW, I see an additional problem. You aren't supposed to be able to use
access modifiers such as public/abstract in an interface definition.
This is something we have to fix.
It should be:
interface Drawable {
function draw();
}
I would be
Marcus, thanks for the heads ups.
I actually did have a (convoluted) example of using protected/private on
interface methods, but reading your explaination makes it clear that
there is a Better Way(tm).
static in interfaces does indeed seem valid: I hope that finds its way
into 'the fold'.
kin
An interface is a *public* contract by definition; PPP specifiers just
don't make sense there.
Neither does static, since interfaces are instance based.
--Wez.
On Tue, 12 Oct 2004 09:34:00 +0200, Jochem Maas <[EMAIL PROTECTED]> wrote:
> I would be very grateful if you could explain the logic beh
Wez Furlong wrote:
An interface is a *public* contract by definition; PPP specifiers just
don't make sense there.
out of curiosity:
would that be a definition at the PHP level (i.e. decided by php-devs)
or is that definition more widely acknowledged (for want of a better
word) (e.g. php-devs used
Hi,
loginfo.pl is not sending commit mails out for pear-core any more, error
messages are:
Use of uninitialized value at /repository/CVSROOT/loginfo.pl line 68.
Use of uninitialized value at /repository/CVSROOT/loginfo.pl line 71.
Use of uninitialized value at /repository/CVSROOT/loginfo.pl line 8
Hi.
My name's André and I'm new on this list; I'd like to
help in the development of PHP. Which tools do I need
for helping in the development?
Thanks for your attention and sorry about the poor
English.
André Thiago.
__
--- Begin Message ---
Jochem Maas wrote:
Wez
Furlong wrote:
An interface is a *public* contract by
definition; PPP specifiers just
don't make sense there.
out of curiosity:
would that be a definition at the PHP level (i.e. decided by php-devs)
or is that definition m
Hi Jason,
Thanks for the info.
I understand how the definition of 'interface' lead logically to
the conclusion that it must be public - I was theorizing a situation
where an interface could be used accross a 'classtree'* in a protected
manner (which could conceptually be seen as as public interfa
Wez Furlong wrote:
Two or three comments:
- You leak the dynamically allocated buffer returned by X509_NAME_oneline()
- X509_NAME_oneline() man page says that its use is discouraged in
favour of smarter functions. Is there a possibility that someone will
need that functionality?
- if you can solve
On Tue, 12 Oct 2004 14:47:05 -0400, Greg MacLellan
<[EMAIL PROTECTED]> wrote:
> Now uses X509_NAME_print_ex(), using the XN_FLAGS_RFC2253 option.
Looks much better now
> bool openssl_csr_subject(mixed csr, string &out)
>
> Now, I don't do very much C coding, and I'm pretty new to the zend API..
Forgive me if this sounds like a newbie type question, but hopefully
someone has some advice for me. I am wanting to distribute an
extension I wrote for PHP and was wondering what the best way to
compile it for all platforms would be. I am completely comfortable
compiling the extension under Linux
- Original Message -
From: "Jeremy Johnstone" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 12, 2004 3:53 PM
Subject: [PHP-DEV] Compiling extensions
> Forgive me if this sounds like a newbie type question, but hopefully
> someone has some advice for me. I am wanting
Wez Furlong wrote:
If you can make that change and then either put the diff online, or as
a regular MIME plain text attachment and not inlined, so that it is
easy to get at without it being mangled in the email, I will apply it
to CVS.
Done. It actually didn't come out mangled for me at all (mo
Hello André,
You can contact me (in provaite please) if you need any help in Portuguese.
--
Rubem Pechansky · Hypervisual
http://hypervisual.com · http://hypervisual.com.br
Tel. +55 (51) 3231 0888 · Fax +55 (51) 3235 2075
---
I must admit that I think it's kind of ugly to be able to reset it by using
"" but as this seems to be the existing behavior (I guess the person that
added the callable support missed this part), I'll apply the patch.
Thanks,
Andi
At 11:44 PM 10/11/2004 -0700, Robert Silva wrote:
The problem is
I see Marcus has already attempted to fix this even though the bug report
is still open.
Marcus, what exactly did you do? It seems you allow only NULL to reset
exception handler and not empty string. Right?
So it seems like you agree with me that "" is ugly but the question is if
we're breaking
We were discussing adding a per class (zend_class_entry *) callback for
constants. It might make sense to allow that and if the callback is NULL
then try the constant's hash in zend_class_entry.
That should solve all cases, right?
Andi
At 11:54 PM 10/11/2004 -0700, Robert Silva wrote:
This patch
At 02:46 PM 10/12/2004 +0200, Jochem Maas wrote:
Wez Furlong wrote:
An interface is a *public* contract by definition; PPP specifiers just
don't make sense there.
out of curiosity:
would that be a definition at the PHP level (i.e. decided by php-devs) or
is that definition more widely acknowledged
I have proposed it to PECL a while back (like June I think), not sure
on the status of the proposal though. Because of the nature of why I
am using this extension, I need to precompile it for as many platforms
as possible and use it as a dynamically loaded module (it's basically
a script licensing
Hello Andi,
Tuesday, October 12, 2004, 11:43:11 PM, you wrote:
> We were discussing adding a per class (zend_class_entry *) callback for
> constants. It might make sense to allow that and if the callback is NULL
> then try the constant's hash in zend_class_entry.
> That should solve all cases,
At 12:34 AM 10/13/2004 +0200, Marcus Boerger wrote:
Hello Andi,
Tuesday, October 12, 2004, 11:43:11 PM, you wrote:
> We were discussing adding a per class (zend_class_entry *) callback for
> constants. It might make sense to allow that and if the callback is NULL
> then try the constant's hash in z
On Tue, 12 Oct 2004 17:08:03 -0500, Jeremy Johnstone <[EMAIL PROTECTED]> wrote:
> I have proposed it to PECL a while back (like June I think), not sure
> on the status of the proposal though.
If you want to get it into PECL, give us a nudge over there to refresh
our collective memories what it is
Hello Andi,
Wednesday, October 13, 2004, 12:37:36 AM, you wrote:
> At 12:34 AM 10/13/2004 +0200, Marcus Boerger wrote:
>>Hello Andi,
>>
>>Tuesday, October 12, 2004, 11:43:11 PM, you wrote:
>>
>> > We were discussing adding a per class (zend_class_entry *) callback for
>> > constants. It might mak
Interfaces describe how to talk to objects (or endpoints, if you're in
to RPC) and so always have an instance (or handle) to talk to. Since
static methods have no instance, they have no meaning in the context
of interfaces--there is nothing to talk to.
IMO.
I'm +1 for simplicity here :-)
--Wez
On Tue, 12 Oct 2004 23:43:27 +0100, Wez Furlong <[EMAIL PROTECTED]> wrote:
> On Tue, 12 Oct 2004 17:08:03 -0500, Jeremy Johnstone <[EMAIL PROTECTED]> wrote:
> > I have proposed it to PECL a while back (like June I think), not sure
> > on the status of the proposal though.
>
> If you want to get it
On Tue, 12 Oct 2004 17:56:45 -0500, Jeremy Johnstone <[EMAIL PROTECTED]> wrote:
> Will do last I heard about it you (and others) were wanting me to
> extend the extension to include a lot more. Unfortunately I haven't
> had the time I wanted to do that.
Getting the code into PECL could result in o
> > Will do last I heard about it you (and others) were wanting me to
> > extend the extension to include a lot more. Unfortunately I haven't
> > had the time I wanted to do that.
>
> Getting the code into PECL could result in other people helping you
> out, depending on how much they want those f
hi,
this patch against php-5.0.2 adds a stream_socket_create_pair()
function. it's nearly identical to socket_create_pair() except it
returns streams instead of socket resources.
i'm currently rewriting a sockets daemon framework using streams with
the added benefit of ssl and other stream good
At 05:23 PM 10/12/2004 -0700, Robert Silva wrote:
Going through the PHP 5 Bug Summary Report looking for stuff I may be able
to help out with and finding a lot of them that are fixed in current cvs but
are still marked as open. I'm curious when you determine a bug to be fixed
and mark it as such. I
The essence of the patch is ok, it's just the checking of the type and
domain args that is too magical.
Probably the best thing to do is register integer constants for
AF_INET etc., but name them STREAM_AF_INET, STREAM_AF_INET6,
STREAM_AF_UNIX, STREAM_SOCK_STREAM and STREAM_SOCK_DGRAM. Look for
R
It seems that everytime I commit to Zend CVS the commit message isn't sent
out. For other's it works.
It might be due to the warnings I'm getting. Does anyone have an idea what
the problem could be?
Checking in zend_compile.c;
/repository/ZendEngine2/zend_compile.c,v <-- zend_compile.c
new rev
> > The patch shown is what SuSE did for their RPM distribution of PHP.
> >
> > One solution may be with the --with-= directive is to assume
that
> > dir may be an absolute path as well.
> >
> > --with-domxml=/usr/lib64
>
> No, this is too different from what PHP always has been doing... thus
a
>
> the patch is here : http://si.kz/~six/stream_socket_create_pair_patch.tgz
>
To add to Wez's comments, I'd rather see it return an array of socket
streams (or FALSE on failure), rather than return true and tuck the streams
into a by-ref parameter.
-Sara
--
PHP Internals - PHP Runtime Develop
34 matches
Mail list logo
