On Mon, Sep 8, 2008 at 12:11 AM, Jochem Maas [EMAIL PROTECTED] wrote:
if anyone knows of some details info on how to
keep multiple installs of
php around (including apache modules) and being able to switch between them
with minimal fuss then
I be very happy to learn!
the easiest option is
Hi Sotiris,
Am Samstag, den 06.09.2008, 15:42 +0300 schrieb sotiris karavarsamis:
i've got a webserver which runs php 5.2.3 via fastcgi, and i've recently
tried to remove the x-powered-by header for security reasons. however,
[...]
Please try the latest 5.2 with expose_php=0. I can't
On Mon, Sep 8, 2008 at 1:18 PM, Jochem Maas [EMAIL PROTECTED] wrote:
P.S. is the missing ext/iconv/php_have_ibm_iconv.h a problem with the src
bundle or
something specific to MacOSX? either way it seems to be the only thing
stopping me from
building 5.3 with all extensions I use.
This file
Hi Jani,
Am Sonntag, den 07.09.2008, 14:33 +0300 schrieb Jani Taskinen:
There are some bugs that have to be fixed before any actual release can be
even
dreamed of: http://bugs.php.net/search.php?cmd=displaystatus=Critical
Note that 2 of those even have patches attached to fix them..
Hi,
I have written a patch to implement upload progress feedback in session data.
The file upload feature in PHP allows extensions to be called back on some
events. A few extensions use this to implement some sort of upload progress
feedback, but none of them are released with PHP, which makes
On 08.09.2008 00:11, Jochem Maas wrote:
--with-xmlrpc
This extension requires iconv.
I have to admit there is a mess with iconv. IMO configure should fail
if one tries to build xmprpc with iconv disabled instead of silently enabling it.
the error message from make is:
In file included
Jochem Maas [EMAIL PROTECTED] writes:
Alexey Zakhlestin schreef:
On Mon, Sep 8, 2008 at 12:11 AM, Jochem Maas [EMAIL PROTECTED] wrote:
if anyone knows of some details info on how to
keep multiple installs of
php around (including apache modules) and being able to switch between them
with
Hi,
Am Montag, den 08.09.2008, 11:44 +0200 schrieb Lars Strojny:
So it is a bug.
Read as: if we can reproduce it in one of our current versions, it is a
bug :)
cu, Lars
--
Jabber: [EMAIL PROTECTED]
Weblog: http://usrportage.de
signature.asc
Description: Dies ist ein digital signierter
hi Lars,
On Mon, Sep 8, 2008 at 12:13 PM, Lars Strojny [EMAIL PROTECTED] wrote:
Hi Jani,
Am Sonntag, den 07.09.2008, 14:33 +0300 schrieb Jani Taskinen:
There are some bugs that have to be fixed before any actual release can be
even
dreamed of:
On Mon, Sep 8, 2008 at 12:18 PM, Arnaud Le Blanc [EMAIL PROTECTED] wrote:
Hi,
I have written a patch to implement upload progress feedback in session data.
The file upload feature in PHP allows extensions to be called back on some
events. A few extensions use this to implement some sort of
On Mon, Sep 8, 2008 at 12:18 PM, Arnaud Le Blanc [EMAIL PROTECTED] wrote:
The patch allows to store upload progress informations in session variables.
These informations can be retrieved by an other script while the upload is
still in progress, allowing to provide feedback to the user.
sotiris karavarsamis escribió:
i've got a webserver which runs php 5.2.3 via fastcgi, and i've recently
tried to remove the x-powered-by header for security reasons.
I hope you are kidding .. do you still think that security through
obscurity has any value ?
--
A computer is like an Old
Hi,
On Monday 08 September 2008 13:03:11 Pierre Joye wrote:
On Mon, Sep 8, 2008 at 12:18 PM, Arnaud Le Blanc [EMAIL PROTECTED]
wrote:
Hi,
I have written a patch to implement upload progress feedback in session
data.
The file upload feature in PHP allows extensions to be called back
Hi,
On Monday 08 September 2008 13:06:50 Martin Jansen wrote:
On Mon, Sep 8, 2008 at 12:18 PM, Arnaud Le Blanc [EMAIL PROTECTED]
wrote:
The patch allows to store upload progress informations in session
variables.
These informations can be retrieved by an other script while the upload is
PHP 6 Bug Database summary - http://bugs.php.net/
Num Status Summary (67 total -- which includes 30 feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
Alexey Zakhlestin schreef:
On Mon, Sep 8, 2008 at 12:11 AM, Jochem Maas [EMAIL PROTECTED] wrote:
if anyone knows of some details info on how to
keep multiple installs of
php around (including apache modules) and being able to switch between them
with minimal fuss then
I be very happy to learn!
Hi,
[...__(set|get|unset|isset)static()...]
Patch looks pretty good. Plaease add __issetStatic and __unsetStatic.
Then provide tests and submit to HEAD. For 5.3 Lukas and Johannes have to
agree but I am sure they first want to see it in HEAD.
Hope we havent missed any other we need to make
Hi Christian,
Am Montag, den 08.09.2008, 05:29 -0400 schrieb Cristian Rodríguez:
[...]
I hope you are kidding .. do you still think that security through
obscurity has any value ?
Doesn't matter. expose_php=Off should definitely disable that header
too. So it is a bug.
cu, Lars
--
Jabber:
Pierre Joye wrote:
hi Lars,
On Mon, Sep 8, 2008 at 12:13 PM, Lars Strojny [EMAIL PROTECTED] wrote:
Hi Jani,
Am Sonntag, den 07.09.2008, 14:33 +0300 schrieb Jani Taskinen:
There are some bugs that have to be fixed before any actual release can be even
dreamed of:
On Mon, Sep 8, 2008 at 3:13 PM, Jani Taskinen [EMAIL PROTECTED] wrote:
Large integer and large file support are planed for php6.
And who decided that? The patches exist, what's preventing us from adding
this long overdue support (originally planned for 5.1!!!) ??
The patches do not exist,
2008/9/8 Arnaud Le Blanc [EMAIL PROTECTED]:
Hi,
On Monday 08 September 2008 13:06:50 Martin Jansen wrote:
On Mon, Sep 8, 2008 at 12:18 PM, Arnaud Le Blanc [EMAIL PROTECTED]
wrote:
The patch allows to store upload progress informations in session
variables.
These informations can be
Jani Taskinen wrote:
There are some bugs that have to be fixed before any actual release can
be even dreamed of:
http://bugs.php.net/search.php?cmd=displaystatus=Critical
Note that 2 of those even have patches attached to fix them..
I had a quick look at bug
Hi,
On Monday 08 September 2008 15:19:07 Richard Quadling wrote:
2008/9/8 Arnaud Le Blanc [EMAIL PROTECTED]:
Hi,
On Monday 08 September 2008 13:06:50 Martin Jansen wrote:
On Mon, Sep 8, 2008 at 12:18 PM, Arnaud Le Blanc [EMAIL PROTECTED]
wrote:
The patch allows to store upload
On Mon, Sep 8, 2008 at 5:30 PM, Christian Schneider
[EMAIL PROTECTED] wrote:
I had a quick look at bug
http://bugs.php.net/bug.php?id=45928
and found the problem to be in Zend/zend_stream.c function
zend_stream_fsize(): It uses fstat() to determine the filesize which on
MacOS X for
Hello All,
There is no way around it given the feedback I am seeing about
namespace usage in the wild, to warm up this old post again.
This post and the additional commentary, especially about performance
by Stas can be found in the archives at:
Hi!
I think given the feedback from users, we really need to actually
benchmark the performance slow down that Greg's proposed changes will
bring. I also guess there are two types of users out there:
Could you summarize the feedback?
The slowdown is obvious - exhaustive autoloading search
On 08.09.2008, at 18:52, Stanislav Malyshev wrote:
Hi!
I think given the feedback from users, we really need to actually
benchmark the performance slow down that Greg's proposed changes
will bring. I also guess there are two types of users out there:
Could you summarize the feedback?
Hi!
Just use single quotes then.. where the hell isn't portable? Windows?
What in this isn't portable???
AFAIK single quotes don't work with tests in --INI-- now. What happens
is that runtest adds some quoting (didn't have time to check it yet)
that makes the resulting value have single
Hi,
I suppose since I use autoload and classes I belong to the first group.
Thing is, we still do care about performance.
I currenly use underscores as some other programmers do, to fake
namespaced identifiers, and from my tests and this discussion so far I'm
convinced the namespaces as
Hi!
So I'd say, make it explicit and remove the vague moment.
Do I understand right that you advocate having to use ::Exception each
time you need the internal class?
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL
Hi!
I am mainly baseing myself on the feedback I got at:
http://pooteeweet.org/blog/1288
OK, will read through it.
I think Liz summarized the gripes best (especially the second paragraph
is important to note):
I've been using namespaces since then went into 5.3. From my experience
Hi!
So I'd say, make it explicit and remove the vague moment.
Do I understand right that you advocate having to use ::Exception each
time you need the internal class?
As I said:
I heard lots of objections how ugly it is to prepend everything with ::
(not
that this is the only possibly
Stanislav Malyshev wrote:
Hi!
I am mainly baseing myself on the feedback I got at:
http://pooteeweet.org/blog/1288
OK, will read through it.
I think Liz summarized the gripes best (especially the second
paragraph is important to note):
I've been using namespaces since then went into
[some comments below]
Lukas Kahwe Smith wrote:
On 08.09.2008, at 18:52, Stanislav Malyshev wrote:
Hi!
I think given the feedback from users, we really need to actually
benchmark the performance slow down that Greg's proposed changes will
bring. I also guess there are two types of users
Hi!
This doesn't work at all
The closest you can do is
?php
use Foo::Bar as F;
F::myfunction;
?
That's the right way to go. If you want functions in global space, put
them there. If not, then use namespace syntax. BTW, what is so bad in
F::myfunction that it makes it absolutely useless?
hi Stas,
On Mon, Sep 8, 2008 at 7:25 PM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
Hi!
Just use single quotes then.. where the hell isn't portable? Windows?
What in this isn't portable???
AFAIK single quotes don't work with tests in --INI-- now. What happens is
that runtest adds some
Stanislav Malyshev wrote:
Hi!
Personally I don't see the point of of having functions in namespaces if
you can't use them in a global scope.
You mean, if you can do foo() it has a point but if it's F::foo() it
doesn't? Then I think your point was purely cosmetical from the start
and
Hi!
What is YOUR suggestion? Just tell us how hilarious it is to type ::
and introduce all the other problems anyway.
Use short class name in 95% of the cases where it is unambiguous (i.e.
there's no class name in this namespace which collides with internal
class name). Use use ::Foo or use
Stanislav Malyshev wrote:
Hi!
For me they are ways to package up code without interfering with built
in PHP functions or other libraries I wish to use.
Right, I agree.
I don't want to retrain myself or others to call all functions in my
code as though they were static methods. I want
Stanislav Malyshev schreef:
Hi!
This doesn't work at all
The closest you can do is
?php
use Foo::Bar as F;
F::myfunction;
?
That's the right way to go. If you want functions in global space, put
them there. If not, then use namespace syntax. BTW, what is so bad in
F::myfunction that it
Elizabeth M Smith schreef:
Stanislav Malyshev wrote:
Hi!
Personally I don't see the point of of having functions in namespaces if
you can't use them in a global scope.
You mean, if you can do foo() it has a point but if it's F::foo() it
doesn't? Then I think your point was purely cosmetical
Stanislav Malyshev wrote:
Hi!
And what happens when you have two libraries and each has their own Date
implementation? How is that any different? If you could alias in
functions, you'd simply alias them in differently - call one _() and one
new_gettext - that's the point of aliasing, to
Hi!
for the same reason you would want it with classes?? because you can
do it with classes, no? and that seems acceptable to you, no? then
functions
should have the same privilege.
Functions and classes are rather different things. Class represents, as
you know, group of data and
On 08.09.2008, at 19:53, Dmitry Stogov wrote:
The main PHP namespaces ideas come from Java packages and Java classes
have to write these use statements in the same way. It's not the end
of the world. I believe that well-designed frameworks won't require a
lot of use statements in user-space
On Mon, 2008-09-08 at 14:39 -0400, Elizabeth M Smith wrote:
Stanislav Malyshev wrote:
Hi!
And what happens when you have two libraries and each has their own Date
implementation? How is that any different? If you could alias in
functions, you'd simply alias them in differently - call
On Mon, 2008-09-08 at 14:45 -0400, Robert Cummings wrote:
On Mon, 2008-09-08 at 14:39 -0400, Elizabeth M Smith wrote:
Stanislav Malyshev wrote:
Hi!
And what happens when you have two libraries and each has their own Date
implementation? How is that any different? If you could alias
Stanislav Malyshev wrote:
If functions in namespaces won't have the same treatment or features as
classes why bother ;)
Functions can't have the same features as classes, because then they'd
be classes :)
That's not what I meant and you know it (sighs)
Bottom line, being able to alias in
Stanislav Malyshev schreef:
Hi!
for the same reason you would want it with classes?? because you can
do it with classes, no? and that seems acceptable to you, no? then
functions
should have the same privilege.
Functions and classes are rather different things. Class represents, as
you
Hi,
On Sep 8, 2008, at 8:45 PM, Lukas Kahwe Smith wrote:
On 08.09.2008, at 19:53, Dmitry Stogov wrote:
The main PHP namespaces ideas come from Java packages and Java
classes
have to write these use statements in the same way. It's not the
end
of the world. I believe that well-designed
Hi!
initial hard work of trying to do something new). Especially in this
sense I would recommend all people on this list to make sure they use
language that encourages people from coming out of the shadows on this
topic, rather than scaring them off.
I can only second that.
But on the other
Antony Dovgal schreef:
On 08.09.2008 00:11, Jochem Maas wrote:
--with-xmlrpc
This extension requires iconv.
aha. well at least that allows me to build 5.3alpha2 with all
the extensions I require to
I have to admit there is a mess with iconv.
I'm glad it's not (just) down to my
Stanislav Malyshev schreef:
Hi!
Hi,
I'm not going to do this offlist with you,
guns are dangerous yet they are sold by the bucket load. either don't
sell guns or let people decide how to use them, don't sell'em then
dictate
that they can't pull the trigger.
I think it would really help
Stanislav Malyshev wrote:
Hi!
Bottom line, being able to alias in functions the same way you can
classes would be useful. You could also shoot yourself in the foot.
You can alias in classes. You can shoot yourself in the foot with that
as well.
As I already noted in my response to
Hi,
This is a middle-length message with 4 parts.
Part 1:
on-list behavior
Could we all please be more efficient? I don't care whether we get
along, but we do need to solve a problem, and endless rhetorical
flourishes != patches.
Part 2:
namespace examples.
Let's examine a realistic code
Hello mr,
Monday, September 8, 2008, 6:58:19 PM, you wrote:
Hi all,
I'm having problems passing an array to the function call_user_function as
parameter. This is the code:
zval *args[3], *func, *retval;
args maust be *** not **
MAKE_STD_ZVAL(func);
MAKE_STD_ZVAL(retval);
Quoting Greg Beaver [EMAIL PROTECTED]:
Part 3:
judgment of value
Current approach:
advantages:
1) internal classes resolve very fast
disadvantages:
1) potential unexpected name resolution to internal class when
namespaced classname exists
New approach:
advantages:
1) code runs the same
Hi!
First of all, I'd like to thank Greg for moving discussion to the
constructive way, way of code examples and proposed solutions.
Currently, in order for this code to be autoload-compatible, we need to
use all of the classes:
?php
namespace PEAR2::Pyrus::PackageFile::v2Iterator;
use
Stanislav Malyshev wrote:
Well, I can tell you what's bad for you but I can't stop you from doing
that :) use * is bad for you, but if you insist on simulating it - well,
ok, it's your code.
I suspect even ZF will run into some kind of import * functionality
being needed. Do you really want
Hi!
I suspect even ZF will run into some kind of import * functionality
being needed. Do you really want to tell a user they have to write 18
use statements before using say the DB component? Or for PEAR2? when a
I answered this exactly question about 100 times already. No, you just
import
As you said before - how is it any different from just being able to
call escape(foo) or display(foo); It's a matter of taste. To me
that is not anymore of a meaningful name - just a different syntax and
not one your average wordpress user would know how to handle.
Well, if it's just a matter
Stanislav Malyshev wrote:
Hi!
I answered this exactly question about 100 times already. No, you just
import DB and then do DB::Class1, DB::Class2 etc. up to DB::Class18.
Does nobody ever read anything prior to starting discussing namespaces?
And I'd ask - who wants to do new DB::mysql when
Hi!
And I'd ask - who wants to do new DB::mysql when they can just do mysql?
I do. Because this way I don't have to worry my mysql would clash with
someone other's mysql, and I can have all DB related stuff under one roof.
The common usage of use is going to be to get the name as short
Hi!
And I'd ask - who wants to do new DB::mysql when they can just do mysql?
I do. Because this way I don't have to worry my mysql would clash with
someone other's mysql, and I can have all DB related stuff under one roof.
It can't clash if you don't use someone other's mysql namespace, or
Hi ML,
Short version: Increase the default max_input_nesting_level from 100
to something 150.
Extended version:
I am working on a Compiler written for PHP. Before you criticize me,
let me explain the entire situation.
I work for Doctrine project. Currently we're refactoring the DQL
(Doctrine
Hi!
Currently I'm working on the compiler, which has this BNF:
http://trac.doctrine-project.org/browser/trunk/query-language.txt
I've done a lot of optimizations to be able to not touch the default
nesting input level, but doing that I added a lot of restrictions that
now are my bottlenecks.
Each grammar rule may forward calls and subsequent things to build itself.
So, ConditionalExpression may forward a call and later call itself
again and again, etc.
At last, the number of nested function calls can easily reach 100.
If you need an example... I can spend some time on it to
Hi,
He means recursion depth, not input nesting depth. 5.3 had a proposed fast
function call algorithm which would avoid the stack limit and allow deeper
recursion, was this accepted and how does it affect the limit of 100 nested
calls?
Regards,
Stan Vassilev
Hi!
Currently I'm working
Yeah... recursion depth.
Sorry, I wrongly typed it.
I think it may be cleaner now...
On Mon, Sep 8, 2008 at 11:07 PM, Stan Vassilev | FM
[EMAIL PROTECTED] wrote:
Hi,
He means recursion depth, not input nesting depth. 5.3 had a proposed fast
function call algorithm which would avoid the
While I have loaded 5.3.? changing any of my existing code base to remove
warnings is not likely to happen any time soon since compatibility with users
who are still running older versions of PHP still needs to be maintained.
I've got http://wiki.php.net/doc/scratchpad/upgrade/53 which seems
Hi,
I've got what I hope is the solution to the problem that erases the
performance issue, and a patch to implement it, read on for details.
Stanislav Malyshev wrote:
Currently, in order for this code to be autoload-compatible, we need to
use all of the classes:
?php
namespace
Hi Lester,
Lester Caine wrote:
While I have loaded 5.3.? changing any of my existing code base to
remove warnings is not likely to happen any time soon since
compatibility with users who are still running older versions of PHP
still needs to be maintained.
I've got
71 matches
Mail list logo
