Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115244
MIME-Version: 1.0
In-Reply-To: <17a5d13c061.1239e763788226.6762452577612536613@manuelcanga.dev>
References: <17a588d53cc.f512f451993137.1114693900572862097@manuelcanga.dev>
 <CAFPFaMKS5sbtw56DXsKoEW8-MrN7rnZA8Lq=CQhw2RKe2GSnrg@mail.gmail.com> <17a5d13c061.1239e763788226.6762452577612536613@manuelcanga.dev>
Date: Wed, 30 Jun 2021 19:21:10 +0500
Message-ID: <CAC_PL4xF3LbRFuaHoOidnJUJx+TqpPeADjABu5jZoMKBxT3zBw@mail.gmail.com>
To: Manuel Canga <php@manuelcanga.dev>
Cc: "G. P. B." <george.banyard@gmail.com>, Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Alternative syntax for Nowdoc.
From: office.hamzaahmad@gmail.com (Hamza Ahmad)

Being positive is good but relying on others is not. If you really
believe that your idea is worth considering, I suggest revisiting it.
You can ask your self the following questions:
  - How is it useful?
  - what special thing does it provide with that the current
implementation does not?
  - What could be the better syntax?
  - Does any other language have the similar feature?
  - If yes, what is the benefit?
  - Will your idea cause any BC break?
  - Do your proposed syntax make any confusion?
  - How can you make it further clear?

If you have answers to all of these questions, you can come and
convince the people here. Still, I don't find your proposal till now
that compelling.

Rather considering the opinions shared here as an offence, take them
positively and redesign your thought.

Best

Hamza

On 6/30/21, Manuel Canga <php@manuelcanga.dev> wrote:
>
>  ---- En mi=C3=A9, 30 jun 2021 14:29:40 +0200 G. P. B. <george.banyard@gm=
ail.com>
> escribi=C3=B3 ----
>  > Ignoring the fact that this proposal is way past the cutoff date to be
> able to make it into PHP 8.1 due to how the RFC process works,it seems th=
at
> this feature just came into your mind and you decided to send it onto the
> list without considering its ramifications.Userland contribution and
> opinions on new features (or other internal discussion) is valuable but
> oughts to consider all the ramifications, good and bad, and how it affect=
s
> the language as a whole. I say this because I didn't do this when I start=
ed
> contributing on this list and it made for less than stellar discussions.
>
> Hi, George,
>
> I am not an expert in developing programming languages. However, I don't
> agree with that.
>
> When Dennis Ritchie and Brian Kernighan developed C. They didn't think in
> avoid pointers because of they thought what they could be dangerous.
> Surely when someone invented air planes, he didn't think of risks but
> opportunities
>
> It was my fault. I thought that someone here would propose an idea and if
> this was useful, then everyone would find the best way to put it into cod=
e.
>
> With last Rowan email, I understood that this purpose is useless. However=
,
> if it had been useful, I had expected answers like:
> "hey, Manuel, ``` is dangerous, why don't use other syntax like ...  ?
> or
> "Manuel,  why don't use this for heredoc ?
>
> In one word: Synergy.
>
> Why should this be done?. Because someone can read my purpose and can mod=
ify
> to something better, maybe a great change to the language.
>
> I think so.
>
> Regards,
> Manuel Canga
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>