Re: Re:RE: [PECL-DEV] Publishing a new extension to PECL

Yeah, I found a simple wrapper(https://github.com/phplang/p3). It works all right with my extension. In fact it's not a substitution of PHP-CPP. I do not want anything like that for my extension any more, just plain old Zend. ------------------ Original ------------------ From: "Timandes White"<timands@gmail.com>; Date: Wed, Dec 20, 2017 12:06 PM To: "CismonX"<admin@cismon.net>; Cc: "Anatol Belski"<ab@php.net>; "pecl-dev"<pecl-dev@lists.php.net>; Subject: Re: [PECL-DEV] Re:RE: [PECL-DEV] Publishing a new extension to PECL Hi, Any luck to find a substitution for PHP-CPP? CismonX <admin@cismon.net>于2017年12月20日周三 上午9:37写道： Hi, Thanks for your reply. I've done a few tesing with my extension. I discovered that, just like what the author of PHPCPP has said, there's a significant performance degradation if you build your extension with PHPCPP, especially there's a lot of context switching between native code and userland PHP. Thus, alongside with some other problems, PHPCPP isn't really suitable for an extension used in production. Currently, I'm working on refactoring my extension so that it won't rely on PHPCPP. ------------------ Original ------------------ From: "Anatol Belski"<ab@php.net>; Date: Wed, Dec 20, 2017 04:51 AM To: "CismonX"<admin@cismon.net>; "pecl-dev"<pecl-dev@lists.php.net>; Subject: RE: [PECL-DEV] Publishing a new extension to PECL Hi, > -----Original Message----- > From: CismonX [mailto:admin@cismon.net] > Sent: Saturday, December 9, 2017 3:52 PM > To: pecl-dev <pecl-dev@lists.php.net> > Subject: [PECL-DEV] Publishing a new extension to PECL > > Hello, > > > I'm a student in Tianjin University and a part-time web developer. > I'd like to publish my new extension to PECL so that more people can know > about it and use it in their projects. > > > All information about this extension can be found in the following GitHub > repository. > https://github.com/CismonX/php-asio > > > Now nearly all main features are implemented, except for polling file descriptors > (including those wrapped in a PHP resource) so that it can work > with other > libraries and some PHP core functions (like > stream_socket_server()), and > providing helpers for multithreading with this extension. > > > What else needs to be done in near future is testing for possible bugs, writing > config.m4 script, and a detailed documentation. > Yeah, some tests would in any case make sense. My concern is when bundling to PHPCPP are several points here - PHPCPP, while being a good approach, is not actively supported - the delivery of libphpcpp is questionable for the end user, no current distro supply it IMHO, if you target some wider audience, it would make more sense to have this implementation as a pure PHP extension. I'm myself am also interested to get more C++ used in PHP and was checking PHPCPP in quite some ways, too. Unfortunately the maintenance appears to be quite idly and several issues are still ignored. Fe see the not portable streams implementation and in general the ignorance of the thread safety and cross platform issues There are some more things on that, that I'd see a bit questionable to mark PHPCPP as a ready for a mass use. Just my two cerns. Regards anatol