Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103847
MIME-Version: 1.0
References: <CAOUfkRK15+dOajTWMuoHmR5OP7+pggN4ByMVtJn-Kd9WEaHX8Q@mail.gmail.com>
In-Reply-To: <CAOUfkRK15+dOajTWMuoHmR5OP7+pggN4ByMVtJn-Kd9WEaHX8Q@mail.gmail.com>
Date: Fri, 25 Jan 2019 12:46:59 +0000
Message-ID: <CALKiJKqDdUq9TUxQKDXqzm=fTykQOxm5guP1LLrv6M9vid5HYg@mail.gmail.com>
To: =?UTF-8?B?0JPQu9C10LEg0JbRg9C60L7Qsg==?= <goootlib@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b2874a058047b915"
Subject: Re: [PHP-DEV] New RFC about variables.
From: rowan.collins@gmail.com (Rowan Collins)

--000000000000b2874a058047b915
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 25 Jan 2019 at 10:32, =D0=93=D0=BB=D0=B5=D0=B1 =D0=96=D1=83=D0=BA=
=D0=BE=D0=B2 <goootlib@gmail.com> wrote:

> Hi, my name is Gleb Zhukov.
>
> In my RFC I want to propose to use a new entities(abstractions), like
> *objects*, *structures* and *data* instead of variables. It gives such
> advatege like a mental division of different, independent entities(object=
s,
> structures, data) in any language.
>

Hi Gleb!

This sounds a lot like how Perl uses "sigils" for different data types -
$scalar, @array, %hash

The problem with this in a complex language like PHP is that you soon run
out of different characters for the different types you might want to
represent. Note that your example already fails in this regard, because it
suggests "#", which is already used for comments.

When designing a language for the first time, it's an interesting thing to
consider, but in an established language like PHP, it would be very
disruptive, and I don't think it brings that much benefit.

You can get almost the same thing in your own code by naming variables
based on their type (so-called "Hungarian notation").

Regards,
--=20
Rowan Collins
[IMSoP]

--000000000000b2874a058047b915--