Pierre Joye wrote:
if nobody with C hacking skills is feeling sufficient pain over this, the
assumption is that the pool of users is too small or the pain is too small.
sorry for such late reply, but I just joined this group. I'm very interested
in Firebird's future in PHP and I have C skills. However, to answer your
assumption: the pain is too small.
How should we understand that? Too small to actually take care of it?
Perhaps I didn't quote enough of Lukas' posting. I was addressing PDO
support for Firebird. If would be great pain not to have php_interbase,
and if nobody is out there willing to do it, I'd like to step up.
What are the requirements for someone to become an extension maintainer?
With the risk to repeat myself, the goal is to have a long term
working extension with maintainer(s). An extension without
maintainers, especially DB related extensions (or service specific
extension) will slowly die within a couple of years if nothing is
done.
Let forget PDO for now, that's not the point (even if a working
firebird support for PDO would rock).
Ok.
What do I need to become a maintainer of php_interbase?
I got C/C++ skills and an very familiar with Firebird (I'm part of the
team that makes FlameRobin, which is an open source cross-platform C++
admin. tool for Firebird). I have access to Linux and Windows XP.
Although I prefer Linux for development, I could compile something with
MSVC Express Edition if/when it's really needed.
Now, when we're at it, my experience with MSVC and Windows command line
tools is almost none. I tried to build PHP 5.3 with it, but the guide on
PHP website has some errors (some stuff just isn't where it says it is,
and it seems some steps are skipped. Also, the 'configure' script used
for MSVC fails to detect that those things are missing). Where should I
report such problems? (Is this list appropriate for such questions)?
Thanks,
--
Milan Babuskov
http://www.flamerobin.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
