On 06/01/2012 12:48 AM, Gustavo Lopes wrote:
> If the RMs are unwilling to do such merging, we should change the policy to
require updating the
> NEWS files in every stable branch to which the fix was merged.
This makes sense to me.
Chris
--
christopher.jo...@oracle.com
http://twitter.com/#
Hi,
2012/6/1 Anatoliy Belsky :
> Hi,
>
> I'm experiencing an issue adding type hints to the function prototypes.
> The following definition gives the "unknown typehint" error when invoking
> a function
>
> ZEND_BEGIN_ARG_INFO_EX(arg_info_trader_adosc, 0, 0, 4)
> ZEND_ARG_TYPE_INFO(0, high, IS_
On Fri, 01 Jun 2012 11:31:13 -0700, Stas Malyshev wrote:
BreakIterator also exposes other native methods:
getAvailableLocales(), getLocale() and factory methods to build
several predefined types of BreakIterators: createWordInstance()
for word boundaries, createCharacterInstance() for locale
de
Hi,
I'm experiencing an issue adding type hints to the function prototypes.
The following definition gives the "unknown typehint" error when invoking
a function
ZEND_BEGIN_ARG_INFO_EX(arg_info_trader_adosc, 0, 0, 4)
ZEND_ARG_TYPE_INFO(0, high, IS_ARRAY, 0)
ZEND_ARG_TYPE_INFO(0, low, IS_
Hi!
> I've wrapped ICU's BreakIterator and RuleBasedBreakIterator. I stopped
> short of adding a procedural interface. I think there's a larger
> expectation of a having an OOP interface when working with iterators.
> What do you think? If there's no procedural interface, I'll change the
> ins
HI,
On Fri, Jun 1, 2012 at 5:02 PM, Gustavo Lopes wrote:
> In any case, I'll rename the classes before merging.
You may have missed part of my replies. One key part was: to discuss
it before doing anything.
This is only one day discussion and I don't feel like we have a long
term decision abou
eval() does indeed set the response code to 500 upon failure.
Is that a bug? I'll file a report because I don't believe
leaving the response code at 500 is consistent with the
statement from the php.net page about eval():
"If there is a parse error in the evaluated code, eval()
returns FALSE and
Gentlemen,
Regarding this bug report: https://bugs.php.net/bug.php?id=49705
As more developers move away from using regular expressions to parse
HTML and start using DOMDocument, I've noticed that quite a few
stumble over encoding "issues". They're not bugs, because it's
documented (I think) that
On Fri, 01 Jun 2012 15:35:13 +0200, Maciek Sokolewicz wrote:
In my personal opinion, all Intl classes should be prefixed with
Intl. It's not so much that BreakIterator is a very common name, but
rather a very ambiguous name that may point to many different things.
Just by the fact that multiple p
On Fri, 1 Jun 2012 15:56:59 +0200, Nikita Popov wrote:
On Fri, Jun 1, 2012 at 9:57 AM, Gustavo Lopes
wrote:
We currently don't use namespaces in any of the core extensions.
Does anything prevent us from starting to do so?
other symbols in ext/intl are in the global namespace; to put
BreakIte
On Fri, 1 Jun 2012 15:37:30 +0200, Pierre Joye wrote:
On Fri, Jun 1, 2012 at 1:34 PM, Gustavo Lopes
wrote:
So would you have RuleBasedBreakIterator renamed
IntlRuleBasedBreakIterator
too?...
Ideally we would yes, while they are less common and less aimed to be
seen as part of another API.
On Fri, Jun 1, 2012 at 9:57 AM, Gustavo Lopes wrote:
> We currently don't use namespaces in any of the core extensions.
Does anything prevent us from starting to do so?
> other symbols in ext/intl are in the global namespace; to put BreakIterator
> in a new namespace would be inconsistent -- and
hi,
On Fri, Jun 1, 2012 at 1:34 PM, Gustavo Lopes wrote:
> So would you have RuleBasedBreakIterator renamed IntlRuleBasedBreakIterator
> too?...
Ideally we would yes, while they are less common and less aimed to be
seen as part of another API.
>I find it very hard to believe that "BreakIterato
On 01-06-2012 13:34, Gustavo Lopes wrote:
On Fri, 1 Jun 2012 12:58:37 +0200, Pierre Joye wrote:
On Fri, Jun 1, 2012 at 10:02 AM, Benjamin Eberlei
wrote:
How about IntlBreakIterator? I agree with David that the naming is very
weird, it doesn't hint at something from Intl but another crazy spl
i
On Fri, 1 Jun 2012 12:58:37 +0200, Pierre Joye wrote:
On Fri, Jun 1, 2012 at 10:02 AM, Benjamin Eberlei
wrote:
How about IntlBreakIterator? I agree with David that the naming is
very
weird, it doesn't hint at something from Intl but another crazy spl
iterator :-)
Asides from date related cla
hi,
On Fri, Jun 1, 2012 at 10:02 AM, Benjamin Eberlei wrote:
> How about IntlBreakIterator? I agree with David that the naming is very
> weird, it doesn't hint at something from Intl but another crazy spl
> iterator :-)
I agree too. BreakIterator is a very common name and I suspect
possible nami
Hi!
We would like to announce the second RC of the 5.3.14 version. This
is mainly a bugfix release. The release includes a fix for a weakness
crypts() DES implementation (CVE-2012-2143). Please test it and notify
us of any problems you may encounter. The full list of the fixes is as
always in the
How about IntlBreakIterator? I agree with David that the naming is very
weird, it doesn't hint at something from Intl but another crazy spl
iterator :-)
On Fri, Jun 1, 2012 at 9:57 AM, Gustavo Lopes wrote:
> On Fri, 01 Jun 2012 09:40:19 +1000, David Muir wrote:
>
>> Coming from a "pleb", my only
On Fri, 01 Jun 2012 09:40:19 +1000, David Muir wrote:
Coming from a "pleb", my only concern is the name if the class is in
the
global scope. A "BreakIterator" to me sounds like something related
to
breaking out of a looping structure, and not something used for
iterating over various language s
On Thu, 31 May 2012 21:01:50 -0400, David Soria Parra wrote:
We would like to announce the second RC of the 5.4.4 version. This
is mainly a bugfix release. The release includes a fix for a weakness
crypts() DES implementation (CVE-2012-2143). Please test it and
notify
us of any problems you may
20 matches
Mail list logo
