2010/1/13 Derick Rethans :
> On Tue, 12 Jan 2010, Raphael Geissert wrote:
[snip]
> Would it be possible to force short_open_tag to a specific value for
> those applications alone? Perhaps through an .htaccess file? That way,
> Debian keeps the "PHP default" but still allows those apps to work.
R
> -Original Message-
> From: Tim Starling [mailto:tstarl...@wikimedia.org]
> Sent: Wednesday, January 13, 2010 7:19 PM
> To: Stas Malyshev
> Cc: internals@lists.php.net
> Subject: Re: [PHP-DEV] About optimization
>
> Stanislav Malyshev wrote:
> >
> > opcodes can be cached (bytecode caches
Antony
Thanks very much for your reply. And yes, you're right, it IS time to upgrade.
Unfortunately, ldd only shows shared libraries that are automatically loaded.
My php extension is loaded by dlopen, which is not shown by ldd.
I used lsof because it shows all DSO libraries that are loaded
Hi!
Basically a structure like the current zend_op_array would be created on
demand by the executor instead of in advance by the compiler.
I guess we could have strings, etc. put in one big string buffer and
refer to them by 32-bit index, that would probably work with statically
allocated th
Raphael Geissert wrote:
> Rasmus Lerdorf wrote:
>
>> Raphael Geissert wrote:
>>> I'm still looking for a way to warn about the use of open_short_tag not
>>> being explicitly enabled on the PERDIR level. Otherwise the only thing I
>>> see would make applications change would be when the default is
Rasmus Lerdorf wrote:
> Raphael Geissert wrote:
>> I'm still looking for a way to warn about the use of open_short_tag not
>> being explicitly enabled on the PERDIR level. Otherwise the only thing I
>> see would make applications change would be when the default is Off and
>> they break.
>
> But
Philip Olson wrote:
>
> It's worth noting that PHP (as of 5.3) does not distribute a php.ini file
> that contains default values (like php.ini-dist essentially did). So I
> imagine issues arise when distributions want to enable one during the PHP
> install.
>
> Curious, do you enable one of the p
Raphael Geissert wrote:
> I'm still looking for a way to warn about the use of open_short_tag not
> being explicitly enabled on the PERDIR level. Otherwise the only thing I see
> would make applications change would be when the default is Off and they
> break.
But why do you want them to change
>>
>> For example, you discussed changing some ini settings and the possibility
>> of making short tags throw deprecated warnings. So I wouldn't be
>> surprised if there are other changes in your forks.
>
> The change on the ini file is to avoid breaking applications (that
> incorrectly rely o
Rasmus Lerdorf wrote:
>
> Then we have to have logic to differentiate It would make the parser quite a bit more complex if we have to start
> parsing stuff outside of the active open tags. Not sure it is worth the
> effort nor the extra overhead.
>
Isn't something similar already done?
I was
Daniel Convissor wrote:
> Hi Raphael:
>
>> What patch do you want to know more about?
>
> None. I am wondering if there is a resource for lay-people interested in
> installing PHP via packages so they can know any eccentricities they will
> encounter when compared to compiling it themselves.
W
Hi Ralph:
On Wed, Jan 13, 2010 at 06:30:04PM -0600, Ralph Schindler wrote:
> In talking with Stas, it seems that since PHP_INT_MAX+1 is pushed into a
> (float) and since float values are stuffed into 52bit mantissa / 11 bits
> for exponents, we are loosing some precision. That lost precisions
Each distribution can definitely apply different patches, but in the
case of at least one, improper application or "adjustement" of the patch
can lead to security holes by itself.
On 10-01-13 12:00 PM, Raphael Geissert wrote:
> Daniel Convissor wrote:
>
>
>> Hi Raphael:
>>
>> On Tue, Jan 12, 20
Rasmus Lerdorf wrote:
Tim Starling wrote:
1927 bytes (I'll use 64-bit from now on since it gives the most shocking
numbers)
PHP 5.3.3-dev (cli) (built: Jan 11 2010 11:26:25)
Linux colo 2.6.31-1-amd64 #1 SMP Sat Oct 24 17:50:31 UTC 2009 x86_64
php > class C {
php { var $v1, $v2, $v3, $v4
On 01/14/2010 02:55 AM, Bruce Bailey wrote:
> Help!
>
> I was patching out a new version of my PHP extension, with a different
> version as part of the name:
>
> libmyext.so.1.0 is now libmyext.so.2.0
>
> I updated php.ini (extension=libmyext.so.2.0) and restarted apache with the
> graceful op
15 matches
Mail list logo
