> -Original Message-
> From: Richard Quadling [mailto:rquadl...@googlemail.com]
> Sent: 05 May 2010 17:26
> To: PHP internals; PHP Documentation List
> Subject: [PHP-DEV] What is the use of the $replacement
> property in the RegexIterator class.
>
> Hi.
>
> I'm in the process of gett
Hi.
I'm in the process of getting the PHPDoc classes showing the correct
inherited properties and methods (public/protected but not private).
I picked RecursiveRegexIterator (it has the largest number of
xi:includes in the documentation) as a test.
Using php --rc I see that the inheritance chain
Pierre Joye wrote:
On Tue, May 4, 2010 at 2:14 PM, Adam Harvey wrote:
1. Apply Tomas's patch to make case-insensitive lookups
locale-ignorant. Pros: fixes immediate problem. Cons: breaks BC for
case-insensitive function/method name lookups for high-bit characters
in single-byte encodings. (
Zitat von Adam Harvey :
Well, I'm going to assume that people have had whatever say they were
going to. It seems that we have three options, so let's put it to a
vote.
+1 for option 1.
Unless we can have some aliases to fix the problem with some PHP
functions being documented non-all-lower-
On 5 May 2010 12:16, Adam Harvey wrote:
> On 5 May 2010 19:01, Steven Van Poeck wrote:
>> Right. That's what I meant by inconsistent code. The call
>> $logs->getSQLLogger()->logSql("...") would function I presume.
>> The reason your example code does not is because it is inconsistent. You're
>> c
On 29/04/2010 09:45, Hannes Magnusson wrote:
On Thu, Apr 29, 2010 at 10:13, Pierre Joye wrote:
pajoye Thu, 29 Apr 2010 08:13:15 +
Revision: http://svn.php.net/viewvc?view=revision&revision=298759
Log:
- Adieu VC6/7/8, merci pour les bons et loyaux service
What exploits are there for __toString()? Just wondering.
On 05/05/2010 07:50, Dmitry Stogov wrote:
Hi Moriyoshi,
I took just a quick look through the patch, but for me it looks like a
bad idea. Introducing new magic function may bring a lot of troubles and
open a new door for exploit writer (w
On Wed, May 5, 2010 at 1:20 PM, Pierre Joye wrote:
> I don't think that option 2 and 3 can be done in 5.x. However I'm +1
> for option 2 in PHP 6 (whenever it comes).
I meant option 1 and 2.
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtim
On Tue, May 4, 2010 at 2:14 PM, Adam Harvey wrote:
> 1. Apply Tomas's patch to make case-insensitive lookups
> locale-ignorant. Pros: fixes immediate problem. Cons: breaks BC for
> case-insensitive function/method name lookups for high-bit characters
> in single-byte encodings. (Not that we've ev
On 5 May 2010 19:01, Steven Van Poeck wrote:
> Right. That's what I meant by inconsistent code. The call
> $logs->getSQLLogger()->logSql("...") would function I presume.
> The reason your example code does not is because it is inconsistent. You're
> calling $logs->getSqlLogger() instead of $logs->
Hannes Magnusson wrote:
On Wed, May 5, 2010 at 11:41, Steven Van Poeck wrote:
Hannes Magnusson wrote:
2. Make function/method names case-sensitive, per Stan's e-mail. Pros:
fixes problem; brings PHP into line with most other languages; extra
consistency with variables; possible performance
On Wed, May 5, 2010 at 11:41, Steven Van Poeck wrote:
> Hannes Magnusson wrote:
>
> 2. Make function/method names case-sensitive, per Stan's e-mail. Pros:
> fixes problem; brings PHP into line with most other languages; extra
> consistency with variables; possible performance improvement. Cons: BC
Hannes Magnusson wrote:
2. Make function/method names case-sensitive, per Stan's e-mail. Pros:
fixes problem; brings PHP into line with most other languages; extra
consistency with variables; possible performance improvement. Cons: BC
break from current documented behaviour.
There is no wa
On 05.05.2010, at 08:44, Patrick ALLAERT wrote:
> 2010/5/4 Adam Harvey :
>> On 19 April 2010 11:58, Adam Harvey wrote:
>>> As at least some of you would already be aware, there's a
>>> long-standing issue with using PHP in a Turkish or Azeri locale,
>>> namely that case-insensitive lookups withi
On Tue, May 4, 2010 at 14:14, Adam Harvey wrote:
> On 19 April 2010 11:58, Adam Harvey wrote:
>> As at least some of you would already be aware, there's a
>> long-standing issue with using PHP in a Turkish or Azeri locale,
>> namely that case-insensitive lookups within the Zend engine (method
>>
> -Original Message-
> From: a...@adamharvey.name [mailto:a...@adamharvey.name] On Behalf
> Of Adam Harvey
> Sent: 04 May 2010 13:15
> The options are:
>
> 1. Apply Tomas's patch to make case-insensitive lookups
> locale-ignorant. Pros: fixes immediate problem. Cons: breaks BC for
> case
On Wed, May 5, 2010 at 8:44 AM, Patrick ALLAERT wrote:
> 2010/5/4 Adam Harvey :
> > On 19 April 2010 11:58, Adam Harvey wrote:
> >> As at least some of you would already be aware, there's a
> >> long-standing issue with using PHP in a Turkish or Azeri locale,
> >> namely that case-insensitive loo
17 matches
Mail list logo
