Hi! > I see the following options to go about this extension: > > 1) Add a deprecation warning as the functionality will effective cease > to exist in php-src. We don't know if this extension will be taken
As an end user (in this case, PHP developer that needs to use Firebase functionality), I couldn't care less where the source code that compiles to the extension lives - php-src or pecl. So warning me about that is not very useful for me. If it gets moved to pecl, I'll discover it from UPGRADING note, amend my install list to fetch the pecl package and that should be the end of the matter for me. In my opinion, deprecation warnings should be used for functionality that the used needs to remove from the code. That's not what we're doing here - and that's not realistic for us to ask people to do, since it's not likely they'd just drop their DB backend. They'd use PECL package instead, or older version. The proper place to warn about this is the release notes (UPGRADING), not runtime deprecation warnings. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
