All,
I think everything is now moved; cvs checkouts should still be fine, and as
dns changes over, commits will become possible again. (if you need to make a
commit now, please tell your system that cvs.php.net happens to point at
pb11.pair.com)
When dns converges, work will continue on lxr and b
Just a heads up,
we should be moving the cvs apparatus from one server to another in the next
few hours. The only down time will be whilst your dns updates, and this will
_only_ affect cvs COMMITS -- not checkouts.
Thanks for your patience.
James Cox
php sysadmin
--
James Cox :: [EMAIL PROTECTE
Is there a reason or is it a bug that the following code doesn't work anymore?
class Foo {
function bar()
{
echo "bar";
}
}
$method = "bar";
Foo::$method();
parse error, unexpected '('
Jan.
--
http://www.horde.org - The Horde Project
http://www.ammma.de - discover your knowledge
htt
Hi,
I'm not quite sure. Can you send me a patch which includes the shift/reduce
conflicts and I'll try and mess around with it? (I'm a bit busy lately so I
hope I'll find time quickly).
Andi
At 06:02 AM 3/21/2003 -0500, Andrei Zmievski wrote:
Andi and Stas,
Here is reworked version of doc com
Thanks,
working much better now
Rob
- Original Message -
From: "Wez Furlong" <[EMAIL PROTECTED]>
To: "Rob Richards" <[EMAIL PROTECTED]>
Cc: "php-dev" <[EMAIL PROTECTED]>
Sent: Sunday, March 23, 2003 1:10 PM
Subject: Re: [PHP-DEV] Win 32 Build problem
> You are most likely building fro
This one should be fixed now.
SH>> > class Bar {
SH>> function boom() {
SH>> echo "BOOM!\n";
SH>> }
SH>> }
SH>>
SH>> import Bar;
SH>>
SH>> $b = new Bar;
SH>> $b->boom();
SH>> ?>
SH>>
SH>> The import parse error will cause a segfault.
SH>>
I have a fix and will commit it shortly.
Just to confirm this is the same problem that I found here:
you have an older curl installation under /usr, but have 7.10.3 under
/usr/local, right?
--Wez.
On Sun, 23 Mar 2003 [EMAIL PROTECTED] wrote:
> greetings,
>
> Here is a bug in 4.3.2RC1
You are most likely building from the wrong branch.
for PHP5:
co php5
for PHP 4.3.x
co -r PHP_4_3 php4
checking out HEAD from php4 will not work.
--Wez.
On Sun, 23 Mar 2003, Rob Richards wrote:
> I am trying to do a win 32 build from the latest cvs source. After 842
> errors I
On Sun, Mar 23, 2003 at 03:37:03PM +0100, Timm Friebe wrote:
> On Sun, 2003-03-23 at 11:48, Sander Roobol wrote:
> > If you supply a unified diff, I'll commit it.
>
> OK. Attached is a unified diff - the three new files which need to be
> added can be found at:
I've applied your patch, but I did
On Sun, 2003-03-23 at 11:47, Sterling Hughes wrote:
> namespace Foo {
> class Bar {
> function boom() {
> echo "BOOM!\n";
> }
> }
>
> import Bar;
>
> $b = new Bar;
> $b->boom();
> ?>
>
> The import parse
boom();
?>
The import parse error will cause a segfault.
-Sterling
--
"Programming today is a race between software engineers stirring to
build bigger and better idiot-proof programs, and the universe trying
to produce bigger and better idiots. So far, the universe is winning."
- Unk
greetings,
Here is a bug in 4.3.2RC1 when ./configur'ing php --with-curl:
checking for cURL 7.9.8 or greater... configure: error: cURL version
7.9.8 or later is required to compile php with cURL support
curl-7.10.3 is using.
--
PHP Internals - PHP Runti
Sorry, this is way off-topic, but I just got this in the Mandrake troll
list, and couldn't resist.
http://mmenal.nerim.net/fuck_mod_perl.jpg
--
Jean-Michel Dault <[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I am trying to do a win 32 build from the latest cvs source. After 842
errors I am trying to go through them to figure out what the problems are
that I am having.
The largest source of errors seems to be a change made in February to the
use of winsock2.
winsock.h is getting pulled in first from /a
Stanislav Malyshev wrote:
> try {
> } catch($e) {
> }
>
> where $e would catch any exception.
This would even be constistent with the other class type hints.
I could live with that,
Sebastian
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
SH>> phpunit. We shouldn't have an engine-level straightjacket on
SH>> exceptions (more of a response to sebastian's mail than to stas').
I meant something more to the lines of:
try {
} catch($e) {
}
where $e would catch any exception.
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL P
On Sun, 2003-03-23 at 10:33, Wez Furlong wrote:
> We need to do at least one of the following:
>
> 1) Force all exceptions to be descendants of a builtin Exception class
> 2) Force all exceptions to implement a Throwable interface
> 3) Provide a catch-all syntax to the language for exception handl
At 16:33 23.03.2003, Wez Furlong wrote:
We need to do at least one of the following:
1) Force all exceptions to be descendants of a builtin Exception class
2) Force all exceptions to implement a Throwable interface
3) Provide a catch-all syntax to the language for exception handling.
Coming from a
Marcus Börger wrote:
For me it sounds like Sebastian wants to write only one catch
handler but that's not the point of designing with exceptions.
No, that's not what I have in mind.
The following is from PHPUnit/TestCase.php
try {
$this->runTest();
}
catch (AssertionFailedEr
Wez Furlong wrote:
> This is *extremely* important for people writing such things as
> SOAP or RPC servers that want to keep their implementations as
> robust as possible.
I was thinking about those, too.
> While we are at it, lets have the call to undefined method fatal
> error and the type-hi
At 16:24 23.03.2003, Stanislav Malyshev wrote:
SB>> The lack of a common interface of thrown exceptions hinders the
SB>> development of applications like PHPUnit that need to be able to
SB>> work with *every* possible exception.
Don't we have a way to catch any exception in the language yet?
We need to do at least one of the following:
1) Force all exceptions to be descendants of a builtin Exception class
2) Force all exceptions to implement a Throwable interface
3) Provide a catch-all syntax to the language for exception handling.
This is *extremely* important for people writing suc
On Sun, 2003-03-23 at 10:24, Stanislav Malyshev wrote:
> SB>> The lack of a common interface of thrown exceptions hinders the
> SB>> development of applications like PHPUnit that need to be able to
> SB>> work with *every* possible exception.
>
> Don't we have a way to catch any exception in
SB>> The lack of a common interface of thrown exceptions hinders the
SB>> development of applications like PHPUnit that need to be able to
SB>> work with *every* possible exception.
Don't we have a way to catch any exception in the language yet?
--
Stanislav Malyshev, Zend Products Enginee
Sterling Hughes wrote:
> That's a bad thing (imho).
The lack of a common interface of thrown exceptions hinders the
development of applications like PHPUnit that need to be able to
work with *every* possible exception.
--
Sebastian Bergmann
http://sebastian-bergmann.de/
On Sun, 2003-03-23 at 09:19, Sebastian Bergmann wrote:
> Sterling Hughes wrote:
> > Why add a throwable interface?
>
> Because we can then make throw() throw only Throwable objects.
>
That's a bad thing (imho). We shouldn't be enforcing design principles
on the users. Sure, we can make advis
James mentioned this change a looong time ago.
And why would you need notice for this change anyway?
PHP5 is hardly a stable no-touchy-touchy branch anyway, and we really do
need to resolve this module naming issues before we release the
alpha/beta/gamma of PHP5.
--Wez.
On Sun, 23 Mar 2003, Dan
Sterling Hughes wrote:
> Why add a throwable interface?
Because we can then make throw() throw only Throwable objects.
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/
-
On Sun, 2003-03-23 at 11:48, Sander Roobol wrote:
> If you supply a unified diff, I'll commit it.
OK. Attached is a unified diff - the three new files which need to be
added can be found at:
http://sitten-polizei.de/php/sybase-fetch-assoc.xml
http://sitten-polizei.de/php/sybase-unbuffered-query.
How about a bit further of a warning than 24 hours on a weekend?
On Sat, 22 Mar 2003, Sterling Hughes wrote:
> Hi,
>
> Since we're all working on php5-dev now, i think its time to update the
> apache module name of php to php5_module or php_module (I'm for the
> latter).
>
> I'll go ahead and do
On Sun, 2003-03-23 at 01:54, Sebastian Bergmann wrote:
> Sterling Hughes wrote:
> > Log:
> > add a standard Exception class.
>
> Could you please also add a standard Throwable interface and make
> Exception implement it?
>
I was thinking of this, I don't see any practical advantage (and i
di
Quoting Zeev Suraski <[EMAIL PROTECTED]>:
> Should be fixed now. Thanks for the test case!
>
> Zeev
>
> At 17:43 22/03/2003, Jan Schneider wrote:
> >This code run in current code (HEAD):
> >
> >class Foo {
> > var $arr = array();
> >}
> >
> >class FooX extends Foo {
> > function bar()
> >
If you supply a unified diff, I'll commit it.
Thanks,
Sander
On Sat, Mar 22, 2003 at 04:36:13PM +0100, Timm Friebe wrote:
> http://bugs.php.net/bug.php?id=20836
>
> Can someone give me sufficient karma to commit the missing documentation
> or simply apply the patch?
>
> - Timm
>
>
> --
> P
33 matches
Mail list logo
