Re: [PHP-DEV] PHP Modules

2023-04-11 Thread Deleu
On Tue, Apr 11, 2023, 11:32 AM Larry Garfield wrote: > But the same people will still complain just as loudly whenever that is, > because they haven't done anything about it for the past 17 years so > they're not going to now. > Do you know that for a fact or should this statement be classified

Re: [PHP-DEV] PHP Modules

2023-04-11 Thread Larry Garfield
On Tue, Apr 11, 2023, at 1:40 AM, Michael Morris wrote: > This will be long. I've read over the Future Stability thread and taken it > in, and decided to mull over an idea I touched on over a decade ago that I > think might help. Also, in the interceding years the JavaScript community > has overcom

Re: [PHP-DEV] PHP Modules

2023-04-11 Thread Arvids Godjuks
On Tue, 11 Apr 2023 at 04:41, Michael Morris wrote: > This will be long. I've read over the Future Stability thread and taken it > in, and decided to mull over an idea I touched on over a decade ago that I > think might help. Also, in the interceding years the JavaScript community > has overcome

Re: [PHP-DEV] PHP Modules

2023-04-10 Thread Sara Golemon
> On Apr 10, 2023, at 20:40, Michael Morris wrote: > > This will be long. Yes, it's long, so I'm going to focus on a couple things and not quote too much. > I propose PHP Modules to hold new features. What you seem to have described is improved lexical scoping. Rather than a shared "globa

Re: [PHP-DEV] PHP modules (pecl) and PHP codes (pear)

2009-10-29 Thread Samuel ROZE
Le jeudi 29 octobre 2009 à 17:37 +0100, Patrick ALLAERT a écrit : > Yes, but as far as a PHP extension may take hundreds time to develop > than a PHP function. > If the PHP version is fast enough, you will win a huge amount of time, > if not, you will only lose less than 1% of the overall dev time.

Re: [PHP-DEV] PHP modules (pecl) and PHP codes (pear)

2009-10-29 Thread Samuel ROZE
Le jeudi 29 octobre 2009 à 17:35 +0100, Patrick ALLAERT a écrit : > 2009/10/29 Samuel ROZE : > > Le jeudi 29 octobre 2009 à 14:03 +0300, Alexey Zakhlestin a écrit : > >> Usually, it is a good idea to write it in PHP at first and then port > >> to C, if performance is poor > > > > But I lose some ti

Re: [PHP-DEV] PHP modules (pecl) and PHP codes (pear)

2009-10-29 Thread Patrick ALLAERT
2009/10/29 Samuel ROZE : > Le jeudi 29 octobre 2009 à 14:03 +0300, Alexey Zakhlestin a écrit : >> Usually, it is a good idea to write it in PHP at first and then port >> to C, if performance is poor > > But I lose some time ! (Reposting with ML included.) Yes, but as far as a PHP extension may ta

Re: [PHP-DEV] PHP modules (pecl) and PHP codes (pear)

2009-10-29 Thread Samuel ROZE
Le jeudi 29 octobre 2009 à 14:03 +0300, Alexey Zakhlestin a écrit : > Usually, it is a good idea to write it in PHP at first and then port > to C, if performance is poor But I lose some time ! -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/un

Re: [PHP-DEV] PHP modules (pecl) and PHP codes (pear)

2009-10-29 Thread Alexey Zakhlestin
On 29.10.2009, at 12:34, Samuel ROZE wrote: Hi, I'll have to develop a function like "parse_url", but "parse_referrer" which provides informations about the URL (the referrer): provider, keywords, type of search (search, cache, translation, ...), real page url... I don't really know how I'll

Re: [PHP-DEV] PHP modules (pecl) and PHP codes (pear)

2009-10-29 Thread Ferenc Kovacs
On Thu, Oct 29, 2009 at 10:34 AM, Samuel ROZE wrote: > Hi, > > I'll have to develop a function like "parse_url", but "parse_referrer" > which provides informations about the URL (the referrer): provider, > keywords, type of search (search, cache, translation, ...), real page > url... > > I don't r