On 18/08/16 12:39, Rowan Collins wrote:
>> Is starting just a Firebird SQL thing or is it more generally available.
>> I do a few google searches but as usual when searching for things like
>> 'starting' one gets hundreds of pages on 'running' the software and it's
>> other connotations.
>
> I've
On 13/08/2016 08:42, Lester Caine wrote:
Is starting just a Firebird SQL thing or is it more generally available.
I do a few google searches but as usual when searching for things like
'starting' one gets hundreds of pages on 'running' the software and it's
other connotations.
I've never come a
> On 14/08/2016, at 2:47 AM, w...@wkhudgins.info wrote:
>
> On 2016-08-13 04:34, Simon Welsh wrote:
>>> On 2/08/2016, at 8:52 AM, w...@wkhudgins.info wrote:
>>> Hello,
>>> I recently emailed the group about submitting an RFC for str_begins() and
>>> str_ends() functions. The RFC has now been offi
On 2016-08-13 04:34, Simon Welsh wrote:
On 2/08/2016, at 8:52 AM, w...@wkhudgins.info wrote:
Hello,
I recently emailed the group about submitting an RFC for str_begins()
and str_ends() functions. The RFC has now been officially submitted
and is viewable at:
https://wiki.php.net/rfc/add_str_
> On 2/08/2016, at 8:52 AM, w...@wkhudgins.info wrote:
>
> Hello,
>
> I recently emailed the group about submitting an RFC for str_begins() and
> str_ends() functions. The RFC has now been officially submitted and is
> viewable at:
>
> https://wiki.php.net/rfc/add_str_begin_and_end_functions
>
On 04/08/16 06:50, Stanislav Malyshev wrote:
>> I guess that "i" isn't appliable when it have slashes.
>> > In this case, functions should be: strbegins, stribegins, strends,
>> > striends.
>> > In all case, I think that is better a third parameter and keep underlined.
> Please, not stribegins. W
On Fri, Aug 12, 2016 at 8:37 PM, wrote:
> I've updated the RFC to reflect the discussion here and on github. You may
> see it at
> https://wiki.php.net/rfc/add_str_begin_and_end_functions . You can see
> the github PR at https://github.com/php/php-src/pull/2049 .
>
> The motivation for these chan
I've updated the RFC to reflect the discussion here and on github. You
may see it at
https://wiki.php.net/rfc/add_str_begin_and_end_functions . You can see
the github PR at https://github.com/php/php-src/pull/2049 .
The motivation for these changes was to maximize consistency between the
propo
Hi!
> I guess that "i" isn't appliable when it have slashes.
> In this case, functions should be: strbegins, stribegins, strends, striends.
> In all case, I think that is better a third parameter and keep underlined.
Please, not stribegins. We have enough functions with weird names :)
I am ambiva
On 03.08.2016 at 09:59, Lauri Kenttä wrote:
> I only saw you mention strpos, preg_match and substr as (slower)
> alternatives. However, there's already a function called substr_compare
> which is meant for just this kind of comparisons but which is more
> general than your RFC.
Thanks for pointin
Hello,
I only saw you mention strpos, preg_match and substr as (slower)
alternatives. However, there's already a function called substr_compare
which is meant for just this kind of comparisons but which is more
general than your RFC.
function str_begins($a, $b) {
return substr_compare($a,
On Wed, Aug 3, 2016 at 7:44 AM, Yasuo Ohgaki wrote:
> as programmer does not have to know that's the TRUE means.
s/that's/what's/
I shouldn't write mails while writing code :(
--
Yasuo Ohgaki
yohg...@ohgaki.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: htt
On 2016-08-02 18:44, Yasuo Ohgaki wrote:
Hi David,
On Tue, Aug 2, 2016 at 10:36 AM, David Rodrigues
wrote:
Sara Golemon wrote:
Feeling "meh" on it (neither for nor against), but I would consider
consistency with other str*() functions by making case-insensitivity
live in separate functions r
On 02/08/2016 23:44, Yasuo Ohgaki wrote:
It might be okay to have "s" in function names, but if we want to be
consistent,
str_replace -> str_replaces
str_ireplace -> str_ireplaces
IMO, following names are better for consistency.
str_begin
str_ibegin
str_end
str_iend
I think those names mean
Hi David,
On Tue, Aug 2, 2016 at 10:36 AM, David Rodrigues wrote:
> Sara Golemon wrote:
>> Feeling "meh" on it (neither for nor against), but I would consider
>> consistency with other str*() functions by making case-insensitivity
>> live in separate functions rather than as a parameter. e.g.
>>
Sara Golemon wrote:
> Feeling "meh" on it (neither for nor against), but I would consider
> consistency with other str*() functions by making case-insensitivity
> live in separate functions rather than as a parameter. e.g.
> str_begins(), str_ibegins(), str_ends(), end_iends()
I guess that "i" isn
On Tue, Aug 2, 2016 at 7:56 AM, Sara Golemon wrote:
> On Mon, Aug 1, 2016 at 3:52 PM, wrote:
>> I recently emailed the group about submitting an RFC for str_begins() and
>> str_ends() functions. The RFC has now been officially submitted and is
>> viewable at:
>>
>> https://wiki.php.net/rfc/add_s
On Mon, Aug 1, 2016 at 3:52 PM, wrote:
> I recently emailed the group about submitting an RFC for str_begins() and
> str_ends() functions. The RFC has now been officially submitted and is
> viewable at:
>
> https://wiki.php.net/rfc/add_str_begin_and_end_functions
>
Feeling "meh" on it (neither fo
Hello,
I recently emailed the group about submitting an RFC for str_begins()
and str_ends() functions. The RFC has now been officially submitted and
is viewable at:
https://wiki.php.net/rfc/add_str_begin_and_end_functions
The github PR may be found at:
https://github.com/php/php-src/pull/20
19 matches
Mail list logo
