Am 06.10.2022 um 23:40 schrieb David Rodrigues :
> But keep in mind that these features are already intended for PHP, and it
> is not a "feature test" or suggestion. The voting process is mandatory and
> the feature must already be set to "accepted".
Just so I understand what you are saying: You w
> If I start coding an application that relies on these new types, is there
a chance that they'll be removed completely, and I have to rewrite it all?
Imagine that there are users, like me, who would like to test features in
development (mainly in order to provide feedback to the development team)
On Thu, Oct 6, 2022 at 1:12 PM Rowan Tommins
wrote:
> On 06/10/2022 17:41, Alex Wells wrote:
> > For example, Kotlin has recently introduced a new feature - unsigned
> integer types.
>
>
> I'm still struggling to understand what I, as a user, would do about this.
>
> If I start coding an applicat
> On 6 Oct 2022, at 23:12, Rowan Tommins wrote:
>
> On 06/10/2022 17:41, Alex Wells wrote:
>> For example, Kotlin has recently introduced a new feature - unsigned integer
>> types.
>
>
> I'm still struggling to understand what I, as a user, would do about this.
>
> If I start coding an app
On 06/10/2022 17:41, Alex Wells wrote:
For example, Kotlin has recently introduced a new feature - unsigned integer
types.
I'm still struggling to understand what I, as a user, would do about this.
If I start coding an application that relies on these new types, is
there a chance that they'
On 06/10/2022 14:44, Claude Pache wrote:
While it may be difficult to validate an email according to some
IETF’s RFC, the HTML standard has pragmatically adopted a pattern
(used to validate `` fields) that is both readable
and suitable for most practical purposes. See:
https://html.spec.wha
> On 6 Oct 2022, at 16:06, Rowan Tommins wrote:
>
> On 06/10/2022 12:16, Alex Wells wrote:
>> A marker merely just tells the compiler "hey, allow me to use this feature
>> right here", i.e. it denotes a piece of code as allowed to use the feature,
>> not enable it. Effectively, all experimen
> Le 6 oct. 2022 à 10:19, Rowan Tommins a écrit :
>
> You described FILTER_VALIDATE_EMAIL as "notorious for being next to useless";
> that gives us two possibilities:
>
> a) A new function will be just as useless, because it will be based on the
> same implementation
> b) There is a better i
On 06/10/2022 12:16, Alex Wells wrote:
A marker merely just tells the compiler "hey, allow me to use this feature right here",
i.e. it denotes a piece of code as allowed to use the feature, not enable it. Effectively, all
experimental features are just regular features that are "always on" and
> On 6 Oct 2022, at 15:26, Christoph M. Becker wrote:
>
> On 04.10.2022 at 22:42, David Rodrigues wrote:
>
>> I wanted to suggest the possibility of introducing experimental features to
>> PHP.
>>
>> This is an old thread I guess, but I think it's good to reevaluate the
>> situation from tim
On 04.10.2022 at 22:42, David Rodrigues wrote:
> I wanted to suggest the possibility of introducing experimental features to
> PHP.
>
> This is an old thread I guess, but I think it's good to reevaluate the
> situation from time to time, as other languages already do this to some
> extent and PHP
> On 5 Oct 2022, at 20:41, Rowan Tommins wrote:
>
> On Wed, 5 Oct 2022 at 18:07, David Rodrigues wrote:
>
>> Another advantage in this sense is that it would be possible to have a
>> single development branch for PHP 8.1 (current version) and 8.2
>> (development version), for example, with t
On 05/10/2022 22:35, David Gebler wrote:
There are multiple RFC standards for email address format but AFAIK
PHP's FILTER_SANITIZE_EMAIL doesn't conform to any of them.
FILTER_SANITIZE_EMAIL is a very short list of characters which claims to
be based on RFC 822 section 6:
https://heap.space/
13 matches
Mail list logo
