Hello Banko,
I remember that you proposed an ORM written in C/C++ last year around
the same time. Back then I was quite opposed to the idea, saying that
something like this best belongs in userland, and that at most certain
bottleneck features should be moved to C (following the example of
Hi Johannes,
This bug suggests the output buffering re-write in HEAD would be
backported to 5_3: http://bugs.php.net/bug.php?id=42641
Is that still in plan?
I have added it as a To be discussed item on http://wiki.php.net/todo/php53.
Regards,
Robin
--
PHP Internals - PHP Runtime Development
New patches can be found at
http://www.digitalsandwich.com/Patches/index.html
I have fixed the forward_static_call (I am not attached to the name and
am open to suggestions) patch to use a callable. In doing this I also
Looks fine. Would this function solve the problem without additional
Hi All,
One of the proposals for Google Summer of Code is a replacement of the
autoconf part of our current build system. This email is a
clarification of some of the concerns that may arise if it is accepted
as a project.
The current autoconf system is written using the macro processing
My two US cents :).
On Mar 19, 2008, at 9:17 PM, Jani Taskinen wrote:
Here is a quick run down of some of the features of CMake and tools
associated with it:
• A single configure script that would be used regardless of the OS
• A much simpler scripting language
m4 is simple. :-p
Since
Gwynne Raskind wrote:
My two US cents :).
On Mar 19, 2008, at 9:17 PM, Jani Taskinen wrote:
Here is a quick run down of some of the features of CMake and tools
associated with it:
• A single configure script that would be used regardless of the OS
• A much simpler scripting language
m4 is
On Tue, Mar 18, 2008 at 4:04 PM, Etienne Kneuss [EMAIL PROTECTED] wrote:
Hello,
the forward_static_call looks like a decent non-intrusive solution,
and your patch looks
good from what I can tell! I guess you should commit it so it can be
documented and all.
If by 'you' you mean me...I
