Litespeed != lighttpd
In any case, we've always been pretty liberal about these kind of SAPI
extensions in order to ensure out-of-the-box experience for our users.
Esp. as litespeed are willing to support it and we have precedence of
Web servers which are far less common I really don't think there
On 3/23/08 5:05 AM, Sebastian Bergmann wrote:
Johannes Schlüter schrieb:
I said in some previous post I won't like multiple namespaces per file
using the 2nd syntax. So imo: either on ns per file and the 2nd syntax
or allow multiple and use brackets. And then I prefer the latter.
I second tha
Hello,
Do we keep the support added in http://bugs.php.net/bug.php?id=37632
(that isn't supported in C++, for instance) or fix the
zend_is_callable_check_func() ?
Thanks.
2008/2/5, Robin Fernandes <[EMAIL PROTECTED]>:
> Hi all,
>
> The fix to bug 37212 (http://bugs.php.net/bug.php?id=37632) in
Hi Pierre,
> Now I'm a bit confused. What are yout talking about now? PHP snapshots
> or PECL snapshots? releases builds?
You can checkout pecl module branch PHP_5_2 and see all the symlinked
extensions there for PHP_5_2, plus intl...
I know that but that does not tell me what you are tal
Hello Andi,
good, and sorry but I really need more tests. Especially some that show
how we do with all the different BOMs.
marcus
Tuesday, March 25, 2008, 1:35:03 AM, you wrote:
> Yes I understand but unfortunately I don't speak Japanese. Rui, is it
> possible for you to try and get more invo
Yes I understand but unfortunately I don't speak Japanese. Rui, is it possible
for you to try and get more involvement from the team that worked on this and
get more tests?
Btw, I think if we use the existing infrastructure Rui and the team built (see
no big reason why not for 5.3) then we can
Hi George,
On Mon, Mar 24, 2008 at 9:27 PM, George Wang <[EMAIL PROTECTED]> wrote:
> It has been over two years since the last time we wrote to the list to
> consider the inclusion of litespeed SAPI module in the stand PHP
> distribution. By that time, our code has been added to CVS repository
On Mon, Mar 24, 2008 at 11:10 PM, Steph Fox <[EMAIL PROTECTED]> wrote:
> Hi Pierre,
>
>
> >>
> >> The only problem is for the snapshots, which
> >> version-dev should we use? My plan was to let the developers define
> >> which branch matches which version (like MYEXT_1_8 for 1.8-dev for
>
Hello Andi,
claiming you have heard doesn't bring us any further though. Please
provide tests other wise I cannot fix and reimplement what is there. Right
now I only got one extremely basic test that only checks for a very very
limited part of what the stuff is designed for.
marcus
Monday, Mar
Andi Gutmans wrote:
Can we please use strlcpy() instead of strncpy()? This is a coding
standard we implemented years ago.
obviously an easy change. FYI - this also needs to be fixed in
fopen_with_path_rel in PHP_5_2, as I copied most of the code from that
function.
Greg
--
PHP Internals -
Hi,
Rasmus Lerdorf schrieb:
Well, popularity-wise it has about 0.003% of the web server market. So
I wouldn't put too much stock in that. We also have yet to ever see a
user request for it.
beside all the other posts about it - regular users don't post requests
that often to the internal
Can we please use strlcpy() instead of strncpy()? This is a coding
standard we implemented years ago.
Thanks.
Andi
> -Original Message-
> From: Dmitry Stogov [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 21, 2008 2:14 AM
> To: Gregory Beaver
> Cc: internals Mailing List; Stas Malyshev
I think many of these encodings are still very much alive. I am pretty sure
that still a large amount of the Japanese market uses Shift-JIS. The majority
of the tools/text editors use this format as opposed to UTF-8.
Andi
> -Original Message-
> From: Alan Knowles [mailto:[EMAIL PROTECTE
Hi Pierre,
The only problem is for the snapshots, which
version-dev should we use? My plan was to let the developers define
which branch matches which version (like MYEXT_1_8 for 1.8-dev for
example). It should be also possible to let the developers define
which branch should be used for
Well, popularity-wise it has about 0.003% of the web server market.
So I wouldn't put too much stock in that. We also have yet to ever
see a user request for it.
As to user request, here is one :-)
http://bugs.php.net/bug.php?id=42987
One of the reasons why did not receive much requests is
Hi,
On Mon, Mar 24, 2008 at 10:00 PM, Steph Fox <[EMAIL PROTECTED]> wrote:
> Re,
>
>
> > "will be maintained only there" means that no more PECL releases will
> > be done. In this case, a notice should be added to tell the users to
> > do not update or use the pecl package anymore (if they use
We have an easy way to do it for released packages, using package.xml.
That's why the PHP version dependency exists.
Please read the rest of my post :)
- Steph
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubs
> The real problem we have is that there's no obvious way to tell if a PECL
> package *release* is geared to a specific branch - and that's only really a
> problem because we effectively have two development branches in PHP at
> present, HEAD and 5_3. Even so, most PECL devs aim to have their c
Re,
"will be maintained only there" means that no more PECL releases will
be done. In this case, a notice should be added to tell the users to
do not update or use the pecl package anymore (if they use a younger
php version than the one where the extension was bundled).
I hear what you're sayi
You are right though, that we have other really odd SAPIs in the core,
but that is mostly a result of never having figured out how build a sapi
module standalone. Most of these really do belong in pecl if we could
solve the standalone issue.
Right, but if we didn't solve it - why we have pi3w
Stanislav Malyshev wrote:
Hi!
I believe, besides the apache SAPI and fcgi SAPI, LiteSpeed SAPI is
one of the top PHP SAPI being used in production environment. And
LiteSpeed SAPI has the combination of best performance, configuration
flexibility via .htaccess and enhanced security with SuEXE
Hi!
I believe, besides the apache SAPI and fcgi SAPI, LiteSpeed SAPI is one
of the top PHP SAPI being used in production environment. And LiteSpeed
SAPI has the combination of best performance, configuration flexibility
via .htaccess and enhanced security with SuEXEC.
I did not look into th
Hi,
It has been over two years since the last time we wrote to the list to
consider the inclusion of litespeed SAPI module in the stand PHP
distribution. By that time, our code has been added to CVS repository
under /pecl/litespeed, and I have been told that "if there is enough
independent us
> Hearing no objections, lets go ahead with this.
>
> Ed, can you move the grapheme support to the intl extension (code, docs,
> tests, etc)?
>
I'll start working on it today. It should go fairly quickly.
=Ed
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: htt
Hannes Magnusson wrote:
> On Sun, Mar 23, 2008 at 3:51 AM, Steph Fox <[EMAIL PROTECTED]> wrote:
>> does anyone have any objection to the proposal at
>> http://wiki.php.net/rfc/peclversioning?
>
> The first step in fixing the core<->pecl relationship? \o/
>
> Looks good.
> But what about extens
Beats me, I'm sure posix-based systems don't, but it is called "Uniform
Naming Convention" so it's possible somebody might implement it
The fact that it's called "uniform" doesn't mean it works in anything
but Windows :) In UNIX IIRC if one needs to access SMB volume the
regular smb:// URLs ar
Steph Fox wrote:
> What a horrible name :) How about pecl_graveyard?
siberia
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Stanislav Malyshev wrote:
>> this would unfortunately break UNC paths on unix, which start with //.
>
> Unix has UNC paths?
Beats me, I'm sure posix-based systems don't, but it is called "Uniform
Naming Convention" so it's possible somebody might implement it
(http://en.wikipedia.org/wiki/Path_(
Steph Fox wrote:
> Oooh
>
>> What a horrible name :) How about pecl_graveyard?
>
> or siberia? :)
>
> - Steph
I vote Siberia - after all that's been the joke all along...
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi Pierre,
Yes, it is what we call the common sense. However it would be even
better to document this common sense so packager (linux distros), new
developers and users will know it.
Yes, that's the plan. But, one thing at a time...
OK, here's a plan. How about we allow 'core' as a version t
Oooh
What a horrible name :) How about pecl_graveyard?
or siberia? :)
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
re,
On Mon, Mar 24, 2008 at 7:05 PM, Steph Fox <[EMAIL PROTECTED]> wrote:
> > Yes, it is what we call the common sense. However it would be even
> > better to document this common sense so packager (linux distros), new
> > developers and users will know it.
>
> Yes, that's the plan. But, one
On Mon, Mar 24, 2008 at 6:08 PM, Andrei Zmievski <[EMAIL PROTECTED]> wrote:
> Precisely. It was never a "secret", despite someone's paranoidal
> proclaiments..
It was not a "secret" per se and someone was not paranoid, please stay
polite and respectful, thank you.
But, there is a huge difference
On Mon, Mar 24, 2008 at 6:05 PM, Steph Fox <[EMAIL PROTECTED]> wrote:
> >> We already have three sets of rules for that (PEAR rules, php-src rules,
> >> version_compare() rules). Basically if version_compare() can deal with
> >> it,
> >> it's in - I don't see how any other approach can be j
this would unfortunately break UNC paths on unix, which start with //.
Unix has UNC paths?
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit
Precisely. It was never a "secret", despite someone's paranoidal
proclaiments..
-Andrei
Stanislav Malyshev wrote:
Those 'few people' were actually in the majority when it was put to
the vote. Yes development could and should've been made public all
along, but the fact remains that intl offers
Dammit, I sat on this record and I broke it..
:)
-Andrei
Pierre Joye wrote:
By the way, when was this list created? Why discussions about the
development of this upcoming core extension are not public and under
php.net? I don't think it is a good thing and I dislike this way of
working.
--
Hi Pierre...
interest (this last mostly for hosting companies) and some kind of
grading
system. But this is all open to discussion and probably won't happen for
a
long while.
I agree with Greg, only the basic info (what we have now) belongs there.
Apparently there are technical reasons
Where is the patch?
Geoffrey Sneddon wrote:
On 21 Mar 2008, at 12:09, Antony Dovgal wrote:
On 03/18/2008 06:51 AM, Stephen Bach wrote:
Attached is a simple proposed patch that fixes Bug 43477. Basically,
the code
that set the error mode of the ICU converter was giving it an
instruction
(the
Hi Steph,
On Mon, Mar 24, 2008 at 3:08 PM, Steph Fox <[EMAIL PROTECTED]> wrote:
> Hello Pierre,
>
>
> >> Aside from Pierre's arguments in favour of using package.xml to set the
> >> extension version (which 3 PECL extensions - two of them Pierre's - do
> >> at
> >> present), does anyone ha
Hello Alan,
that is basically my impression. Although I did not look into who might
be using what in particular. Either way the feature is fully dropped in
HEAD.
marcus
Monday, March 24, 2008, 4:12:54 PM, you wrote:
> Reading through this, It looks like this is aimed at Big5/shiftJS/?
> mayb
Reading through this, It looks like this is aimed at Big5/shiftJS/?
maybe korean??
I know from HK and probably TW, who use Big5 (traditional chinese
encoding), that it's pretty much been phased out with the introduction
of unicode (basically AFAIR Windows 95/98/ME/NT chinese editions used
the
Dmitry Stogov wrote:
>
>
> Gregory Beaver wrote:
>> Dmitry Stogov wrote:
>>> REALPATH_FAILED looks like a hack :(
>>> PHP itself doesn't need it at all, according to your patch
>>> php_stream_open() may just return NULL immediately instead of setting
>>> of this flag.
>>> However I am not sure that
Gregory Beaver wrote:
Dmitry Stogov wrote:
REALPATH_FAILED looks like a hack :(
PHP itself doesn't need it at all, according to your patch
php_stream_open() may just return NULL immediately instead of setting
of this flag.
However I am not sure that it will work for all cases. The fact that
we
Dmitry Stogov wrote:
> REALPATH_FAILED looks like a hack :(
> PHP itself doesn't need it at all, according to your patch
> php_stream_open() may just return NULL immediately instead of setting
> of this flag.
> However I am not sure that it will work for all cases. The fact that
> we cannot resolve
Steph Fox wrote:
> Hello Pierre,
>
>>> Aside from Pierre's arguments in favour of using package.xml to set the
>>> extension version (which 3 PECL extensions - two of them Pierre's -
>>> do at
>>> present), does anyone have any objection to the proposal at
>>> http://wiki.php.net/rfc/peclversi
REALPATH_FAILED looks like a hack :(
PHP itself doesn't need it at all, according to your patch
php_stream_open() may just return NULL immediately instead of setting of
this flag.
However I am not sure that it will work for all cases. The fact that we
cannot resolve the path doesn't mean that w
Hello Pierre,
Aside from Pierre's arguments in favour of using package.xml to set the
extension version (which 3 PECL extensions - two of them Pierre's - do
at
present), does anyone have any objection to the proposal at
http://wiki.php.net/rfc/peclversioning?
I'm not in favour of using p
The direct comparison must be faster than memcmp().
memcmp() might be optimized into the same code but probably won't be.
Thanks. Dmitry.
Marcus Boerger wrote:
Hello Gregory,
Monday, March 24, 2008, 2:47:25 PM, you wrote:
Marcus Boerger wrote:
Hello Gregory,
Monday, March 24, 2008, 2:28:00
Hello Gregory,
Monday, March 24, 2008, 2:47:25 PM, you wrote:
> Marcus Boerger wrote:
>> Hello Gregory,
>>
>> Monday, March 24, 2008, 2:28:00 PM, you wrote:
>>
>>
>>> Index: main/fopen_wrappers.c
>>> ===
>>> RCS file: /repository/
Marcus Boerger wrote:
> Hello Gregory,
>
> Monday, March 24, 2008, 2:28:00 PM, you wrote:
>
>
>> Index: main/fopen_wrappers.c
>> ===
>> RCS file: /repository/php-src/main/fopen_wrappers.c,v
>> retrieving revision 1.175.2.3.2.13.2.9
Hello Alexey,
my last update on this was that people were unhappy with closures. If
that is not the case than maybe we need to write this as an RFC on the
wiki: http://wiki.php.net/rfc
So well maybe you're right and it only requires selecting between the two
and checking whether there are tiny
Hello Gregory,
Monday, March 24, 2008, 2:28:00 PM, you wrote:
> Index: main/fopen_wrappers.c
> ===
> RCS file: /repository/php-src/main/fopen_wrappers.c,v
> retrieving revision 1.175.2.3.2.13.2.9
> diff -u -r1.175.2.3.2.13.2.9 fopen_
Dmitry Stogov wrote:
> Hi Greg,
>
> In your second patch you forgot "break", so it couldn't work.
> I don't see any reason in second patch at all, because you call
> php_resolve_patch() from _php_stream_open_wrapper_ex() anyway.
>
> The bad thing with the first part that it calls realpath() functio
Hello Lars,
to me this makes pretty much sense on a second glance as it perfectly
reflects what our string would do. And for someone learning 'NOWDOC',
using "HEREDOC" seems just natural.
So I am all +1
Consistency and satisfying expectations rocks!
marcus
Saturday, March 22, 2008, 9:17:27 PM,
Hi Greg,
In your second patch you forgot "break", so it couldn't work.
I don't see any reason in second patch at all, because you call
php_resolve_patch() from _php_stream_open_wrapper_ex() anyway.
The bad thing with the first part that it calls realpath() function
twice for each include("rel
On Sun, Mar 23, 2008 at 3:51 AM, Steph Fox <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Since I'm still awake at 3am...
>
> Aside from Pierre's arguments in favour of using package.xml to set the
> extension version (which 3 PECL extensions - two of them Pierre's - do at
> present), does anyone hav
Hi Steph,
Am Sonntag, den 23.03.2008, 01:58 + schrieb Steph Fox:
>
> Just one. Why?
We have double and single quotes for variable assignments. On of the
reasons we use single quotes for NOWDOC was because it is as in variable
assignments. If we follow that argument, there is no reason why
$
PHP 6 Bug Database summary - http://bugs.php.net
Num Status Summary (58 total including feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
===
On 3/23/08, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> Hello Ryusuke,
>
> I have put your proposal as a link to a PHP GSoC 2008 idea here:
> http://wiki.php.net/gsoc/2008
>
> Feel invited to add to this idea in whatever way you want :-)
how is it related to gsoc?
patches are already there — a
60 matches
Mail list logo
