On Mon, Oct 7, 2019, 08:22 Stanislav Malyshev wrote:
> Hi!
>
> > We seem to be experiencing something of a philosophical clash with regard
> > to deprecation. Perhaps we should attempt to establish some general
> > guidelines for deprecation as a group?
>
> I personally thought we had thom - no
Hi!
> We seem to be experiencing something of a philosophical clash with regard
> to deprecation. Perhaps we should attempt to establish some general
> guidelines for deprecation as a group?
I personally thought we had thom - no removing things unless there's a
very good reason to. And yet, we h
On Sun, Oct 6, 2019 at 12:36 PM Zeev Suraski wrote:
> On Fri, 4 Oct 2019 at 17:45 Mark Randall wrote:
>
> > Hi Internals,
> >
> > I put forward the following RFC "Deprecate Backtick Operator (V2)" for
> > discussion.
> >
>
>
> Mark, all,
>
> I’m not sure what planetary alignment or moon phase tr
On Fri, 4 Oct 2019 at 17:45 Mark Randall wrote:
> Hi Internals,
>
> I put forward the following RFC "Deprecate Backtick Operator (V2)" for
> discussion.
>
Mark, all,
I’m not sure what planetary alignment or moon phase triggered this recent
compatibility-breaking onslaught, but it can’t go on l
On 06/10/2019 14:18, Reinis Rozitis wrote:
Since `` are used for literal strings (for poorly chosen reserved words as
field, table names (which happens from time to time)) in MySQL (multiline)
queries I doubt there is a simple way to distinguish and replace everything to
exec().
Hi,
As the
> -Original Message-
> From: Olumide Samson [mailto:oludons...@gmail.com]
>
> it should be deprecated for exec usage since they both do same thing
With that logic This isn't high cost breaking changes coz it has a verifiable, ready
> alternative to upgrade to without huge Regex search