Hi! > Import the library into core and maintain it or write an alternate from > scratch - IF the functions it provides truly has market demand.
Nice suggestion if we had a line of volunteers at our doors asking us to give them something to maintain. We don't. So this is not an option, it's a happy dream. Realistic option is imap support that we have now or no imap support at all. Market demand for functionality is always way exceeds market supply of maintainers, especially long-term maintainers. If we have somebody coming forward and volunteering to write new imap extension (or take over c-client maintainership) - excellent, problem solved. But I don't see it happening now. > Otherwise remove support. Those seem to me like the only logical > options. Nostalgia is not logical. Functionality is logical. We don't have imap module because people need to feel nice about keeping imap module. We have imap module because imap functionality is used. There's a lot of PHP packages using imap on github, if you look. Can they switch? Probably. But let's not pretend that the situation is we're having this module in core out of pure nostalgia. We have it because it's functionality that is needed by people. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
