Don't even think about merging that mess into PHP_5_1 before
I've got it sorted out!
And next time you want to mess around configure/makefiles
ask me before you commit!
--Jani
On Sat, 22 Oct 2005, John Coggeshall wrote:
On Thu, 2005-10-20 at 20:20 +0100, Nuno Lopes wrot
Hi,
DIY, it's not hard. You need a semaphore (*nix) and shared memory . Semaphores
are not available on Windows but they are emulatable with ext/shmop.
More info can be found here :
http://hristov.com/andrey/projects/php_stuff/pres/writing_parallel_apps_with_PHP.pdf
sources :
http://hristov.com/a
On Thu, 2005-10-20 at 20:20 +0100, Nuno Lopes wrote:
> As I've told you before, I had already tested your patch. It has the problem
> in the parsers that have bogus #line directives (but thats another story).
> The other problem is that you don't handle files with the same name.
Yeah I'm aware o
On 10/22/05, techtonik <[EMAIL PROTECTED]> wrote:
> Is there any developers who officially supports PHP 4 branch?
Yes, we "support" people using it, but not so much people building it.
We're trying to shift people on to PHP 5 so that the support burden
is lessened. If you're building it yourself
Jani Taskinen wrote:
>
On Sat, 22 Oct 2005, Sebastian Bergmann wrote:
Rasmus Lerdorf schrieb:
Include an opcode cache by default. A lot of work has gone into
pecl/apc recently, but I am not hung up on which one goes in.
In case we include APC by default, it would be nice if its apc_store(
>
> I don't want to burst your bubble, but PHP 5 is the current release of
> PHP, and we've started work on PHP 6.
Do as you wish, but I though PHP4 is still the most widely supported version
on the web and if you're going to conquer the world you have to think about
those users, who was already
> If you have cygwin flex and bison, you don't need to copy anything.
And if I don't have any? Can it be made as simple as "unpack and compile"?
If you'll read this page
http://www.php.net/manual/en/install.windows.building.php
you notice redundant instructions for copying files and setting up
MS
I don't want to burst your bubble, but PHP 5 is the current release of
PHP, and we've started work on PHP 6. The win32 build system is much
more friendly; I've already spent many hours on making things better
there.
If you want to improve things for PHP 4, go for it, but I don't and
won't have ti
If you have cygwin flex and bison, you don't need to copy anything.
You also don't *have* to recompile resolv.lib; just build a release
build and use that, even when you're building a debug version of PHP.
--Wez.
On 10/22/05, techtonik <[EMAIL PROTECTED]> wrote:
> ||*()*|| Greetings, phpinnards..
Hi Marcus.
Thanks for reviewing the patch!
I agree with you that using environment vars is excessive in this script.
The only reason I've used it is to allow the user to pass arguments to
valgrind (like the suppresions file). After reading the valgrind manual,
I've discovered that it is also p
Jani Taskinen schrieb:
> But I'd treat this kind of thing rather as part of session handling
> mechanism though. We had a short thread about this in the "wishlist"
> thread already so read that too.
Ah, now I remember. Anyways, just wanted to make sure that this does not
get forgotten ;-)
--
S
On Sat, 22 Oct 2005, Sebastian Bergmann wrote:
Jani Taskinen schrieb:
Containing what? What about those "round-robin" environments where
you have several machines serving same web pages?
You're right, what we really need is being able to introduce new
super-globals through extensions (can we
Jani Taskinen schrieb:
> Containing what? What about those "round-robin" environments where
> you have several machines serving same web pages?
You're right, what we really need is being able to introduce new
super-globals through extensions (can we do this already?), so that the
extensions tha
On Sat, 22 Oct 2005, Sebastian Bergmann wrote:
Rasmus Lerdorf schrieb:
Include an opcode cache by default. A lot of work has gone into
pecl/apc recently, but I am not hung up on which one goes in.
In case we include APC by default, it would be nice if its apc_store() /
apc_fetch() mechanism
Antony Dovgal schrieb:
>>> We can consider it as a bugfix, IMO the current typehints are
>>> "broken".
>> Then you should MFH to PHP_5_1, NOW.
> Amen.
Did we reach a conclusion here? I talked to Derick the other day and he
said "maybe" for PHP 5.1.1, but not for PHP 5.1.0 because we're so far
a
Rasmus Lerdorf schrieb:
> Include an opcode cache by default. A lot of work has gone into
> pecl/apc recently, but I am not hung up on which one goes in.
In case we include APC by default, it would be nice if its apc_store() /
apc_fetch() mechanism could be mapped to a new super-global, say
$_
||*()*|| Greetings, phpinnards.. =)
I tried to automate build system for PHP 4 a bit and after that
can't get some stupid questions out of my head. Install instructions
located as usual http://www.php.net/manual/en/install.windows.building.php
There are at least two inconveniences:
1. Need
17 matches
Mail list logo
