Hi!
If we care about binary API compatibility, how about make
PS_MOD_SID2/PS_MOD_FUNCS_SID2
macros? Then we can forget about ABI.
I'm sorry, I don't understand how any macros would help anything. Adding
stuff to the structure would break binary compatibility, how the macros
would help it?
Per RFC: https://wiki.php.net/rfc/propertygetsetsyntax
Alright, getters/setters has been built. This is my first patch to the php
core. Here is what has been implemented:
http://www.clintpriest.com/patches/accessors_v1.patch (patch against trunk)
Asymmetrical getters/setters syntax:
pu
Hi Stats,
2011/12/4 Stas Malyshev :
> Hi!
>
> My main concern with this change is that it is binary incompatible with
> existing session implementation, which means it would be hard to get it into
> 5.3 and 5.4. While I understand sometimes adding handlers is inevitable, in
> this case I'm not sur
Hi!
My main concern with this change is that it is binary incompatible with
existing session implementation, which means it would be hard to get it
into 5.3 and 5.4. While I understand sometimes adding handlers is
inevitable, in this case I'm not sure why it is required. So far the
only reaso
Hi!
If user really want to set session ID, they can explicitly disable
use_strict_mode.
For almost all application, setting static ID is bad code. There are
some applications that exploit adoptive session, but they can live
with new code also.
I'm not sure I understand - why prohibiting the s
On 12/03/2011 10:28 AM, Dmitri Snytkine wrote:
> APC is great, APC definetely speeds up the php a lot but I just remember that
> there used to be also optimization options.
> I remember the days where eAccelerator and php accelerator and mmcache were
> popular. They all had code optimization opt
APC is great, APC definetely speeds up the php a lot but I just remember that
there used to be also optimization options.
I remember the days where eAccelerator and php accelerator and mmcache were
popular. They all had code optimization option to speed up compiled scripts.
Dmitri Snytkine
Web
hi,
see
http://svn.php.net/viewvc?view=revision&revision=224572
and
http://svn.php.net/viewvc/pecl/apc/trunk/TECHNOTES.txt?r1=224572&r2=224571&pathrev=224572
especially
it seems that it doesn't work out, and it was removed.
So I'm pretty sure, that we won't see that option in the future. If the
This feature was described as "experimental" in the documentation.
Maybe the "experiment" didn't work out - or it worked out fine and
equivalent optimizations are part of the normal compliation of PHP
code now?
I would hope the latter - it doesn't seem like a bytecode cache should
have to do optim
I've had a look at making string offsets of strings a bit saner.
At present with the fix for array dereferencing : ?search=hello and a
test like isset($_GET['search']['name']) results in true, which is has
potential security problems and is very confusing for any programmer
finding and worki
The option apc.optimization has been removed in apc 3.0.13
I wonder if there are any plans to put the code optimization option back
into APC, so the APC will be not only the cache of php files but also act as
an accelerator?
Dmitri Snytkine
Web Developer
Ultra Logistics, Inc.
Phone: (888) 220-46
Hi!
if (!(($validator = new SomeValidator())->isValid($value))) {
// Validation failed, get messages...
$view->assign('errors' => $validator->getMessages());
return $view->render('error');
}
// validation passed, do something...
Yes, this could be writ
12 matches
Mail list logo