On Wed, 13 Oct 2004, Hans Zaunere wrote:
> > > As I mentioned in my original post, --with-module and
> > > --with-module-dir seem to have some inconsistencies themselves as
> > > well. What is the behavior?
> >
> > Where are the inconsistencies, can you point those out?
>
> Here are some notes ad
Yeah this is definitely going to be fixed (partially fixed already in CVS)
where you'll get a "You idiot" message if you try and use access modifiers :)
I thought there was another bug you pointed out in your code but I might be
wrong. Can't remember.
Thanks,
Andi
At 10:07 PM 10/13/2004 +0200,
On Tue, 2004-10-12 at 00:09, Andi Gutmans wrote:
> What do you expect to happen?
I expected it to work: Either give me a compile error ("You idiot! Why
are you using method modifiers in an interface?") or not complain and
let me code improper OO. The problem is the the confusing message.
Btw, the
hi,
socket type checking removed :
http://si.kz/~six/stream_socket_pair.notypecheck.diff
Vincent
Wez Furlong wrote:
I wouldn't bother checking against known types; let sockpair() handle that.
It is possible that someone might want/need to use some other value
which we haven't thought of, or are e
Apologies for breaking into a new thread, but I wanted to highlight the
different nature of this post.
> PHP's ./configure needs to be fixed of course, though for now the
> suggested patches are a bit suboptimal iirc. I would like to give it a
> shot, but I'll need to have access to a linux runni
> > > > 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 al
I wouldn't bother checking against known types; let sockpair() handle that.
It is possible that someone might want/need to use some other value
which we haven't thought of, or are even aware of.
--Wez.
On Wed, 13 Oct 2004 15:58:46 +0200, Vincent NEGRIER <[EMAIL PROTECTED]> wrote:
> Here is an upd
On Wed, 13 Oct 2004, Joe Orton wrote:
> > FreeBSD amd64 installs its libraries into /usr/lib, as any
> > sane OS does.
>
> So other than vague slurs on OS sanity,
Hey, even Debian sid does it ;-)
> are there objections to
> committing my --with-libdir patch to HEAD?
>
> http://news.php.n
On Wed, 13 Oct 2004, Joe Orton wrote:
On Wed, Oct 13, 2004 at 09:55:15AM +0200, Sascha Schumann wrote:
Going back to 64bit platforms, this is going to be a problem moving
forward. AMD64 is all over the place, and thus having lib and lib64
That is hardly a new issue. Irix and other systems hav
On Wed, Oct 13, 2004 at 09:55:15AM +0200, Sascha Schumann wrote:
> >Going back to 64bit platforms, this is going to be a problem moving
> >forward. AMD64 is all over the place, and thus having lib and lib64
>
> That is hardly a new issue. Irix and other systems have had
> different lib d
I made the changes so that FALSE is returned :
http://si.kz/~six/stream_socket_pair.noassume.diff
regards,
Vincent
- Original Message -
From: "Andrey Hristov" <[EMAIL PROTECTED]>
Newsgroups: php.internals
To: "Vincent NEGRIER" <[EMAIL PROTECTED]>
Cc: "Wez Furlong" <[EMAIL PROTECTED]>; <[EM
Here is an updated version of the patch :
http://si.kz/~six/stream_socket_pair.diff
It now registers STREAM_AF_* and STREAM_SOCK_* long constants, checks the
domain and type against known types and passes the array of created streams
as return value instead of a byref param... and the diff is agai
Hi,
In the cyrus_connect() php function, the Cyrus function
imclient_connect() is called, and its return value is checked for
0, -1 or -2. There is a problem with that however:
a) imclient_connect() returns in fact 0, -1, -2 OR the value of
errno (if something outside of imclient_connect()'s s
> > 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.
It would look simpler, but on the other
> > Going back to 64bit platforms, this is going to be a problem moving
> > forward. AMD64 is all over the place, and thus having lib and lib64
>
> That is hardly a new issue. Irix and other systems have had
> different lib directories for many years. The users of those
> systems
On Wed, 13 Oct 2004, Sascha Schumann wrote:
> That was an assert, not a fix.
>
> It appears to be a change in how cvs invokes the
> commitinfo/loginfo scripts. I will dig into the issue later,
> unless someone beats me to it.
I know they changed that in later CVS versions. Bu
Going back to 64bit platforms, this is going to be a problem moving
forward. AMD64 is all over the place, and thus having lib and lib64
That is hardly a new issue. Irix and other systems have had
different lib directories for many years. The users of those
systems always coped with t
That was an assert, not a fix.
It appears to be a change in how cvs invokes the
commitinfo/loginfo scripts. I will dig into the issue later,
unless someone beats me to it.
- Sascha
On Wed, 13 Oct 2004, Derick Rethans wrote:
On Tue, 12 Oct 2004, Andi Gutmans wrote:
It seems that
On Tue, 12 Oct 2004, Andi Gutmans wrote:
> 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?
Sascha was doing something with it, and committed
On Tue, 12 Oct 2004, 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
Hans Zaunere wrote:
> I notice a number of strange issues while running ./configure.
For what it's worth: I never experienced any of the problems you
describe with PHP (PHP_4_3, PHP_5_0, HEAD) on my AMD64 box which runs on
Gentoo Linux (~amd64).
--
Sebastian Bergmann http
On Tue, 12 Oct 2004, Hans Zaunere wrote:
>
> > > 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 t
22 matches
Mail list logo