Date: 09/29/00
- Next message: serhiy <email protected>: "[PHP-DEV] PHP 4.0 Bug #6953: convert_cyr_string does not convert Ukrainian chars"
- Previous message: landi <email protected>: "[PHP-DEV] PHP 4.0 Bug #6952: ldapadd and ldapmodify"
- In reply to: Andi Gutmans: "Re: [PHP-DEV] Content of this list???"
- Next in thread: Andi Gutmans: "Re: [PHP-DEV] Content of this list???"
- Reply: Andi Gutmans: "Re: [PHP-DEV] Content of this list???"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andi Gutmans wrote:
>
> Personally I think php-dev is the right forum for discussing any C level
> development, both extension module development and PHP core development
> (which is pretty much the same).
> The reason we aren't sending bug reports to a php-bugs mailing list is
> because the people who can fix bugs are usually on the php-dev mailing list
> and if we'd create a separate mailing list for them it would probably lead
> to only a small amount of people subscribing to the bugs mailing list and
> slow down bug fixing in PHP which I think is a bad thing. If someone is
> REALLY irritated by the bug reports they can filter it out but as a general
> rule I really prefer the C developers who know PHP development, both if
> it's core development or extension development to take time once in a while
> and take a look at incoming bug reports.
> This is why I really think having a separate forum for just extension
> development is not the right way to go because extension development is
> probably the most important development going on in PHP today and it should
> be discussed on the php-dev mailing list. You can't do much with PHP if it
> doesn't have extensions.
> If most people disagree with me we could host a separate mailing list but
> try and think if it's worth it. I personally think it would be a loss for PHP.
>
> Andi
I think you make a valid point (my filter engine feels loved ;) .. I just wanted to make
sure that this list was appropriate for the discussion of extensions that would never be
'released' to the general public, but were rather being developed in-house to solve and
glue in-house systems.
I realize that usually, in most places, data is stored and accessed through some sort of
open standard system (SQL, LDAP, etc .. ) for which the development of extensions benifit
us all, but there exists some places where data is still stored in binary files, accessed
through an internally developed API. I was getting sick of the overhead of writing trivial
tools in C for this data, so I figured I might as well develop an extension so I could get
at the data through PHP. But this wouldn't benifit anyone else. Only me. :) So it isn't
really the development of PHP in so far as the development of our software through the PHP
API.
Anyhow, maybe I'm over explaining. If I can discuss my problems here, then I'm happy. =)
Garret
-- - Garret Thomson ---- Programmer/Analyst ------------------------------ TargetNet.Com Inc | [416]-306-0466 x 919 | gthomson <email protected> "I always wanted to be somebody, but I should have been more specific." - Seinfield ------------------------------------------------------------------------- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: serhiy <email protected>: "[PHP-DEV] PHP 4.0 Bug #6953: convert_cyr_string does not convert Ukrainian chars"
- Previous message: landi <email protected>: "[PHP-DEV] PHP 4.0 Bug #6952: ldapadd and ldapmodify"
- In reply to: Andi Gutmans: "Re: [PHP-DEV] Content of this list???"
- Next in thread: Andi Gutmans: "Re: [PHP-DEV] Content of this list???"
- Reply: Andi Gutmans: "Re: [PHP-DEV] Content of this list???"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

