perl6-language
[Top] [All Lists]

Re: Allowing '-' in identifiers: what's the motivation?

To: perl6-language@perl.org
Subject: Re: Allowing '-' in identifiers: what's the motivation?
From: TSa <Thomas.Sandlass@barco.com>
Date: Tue, 12 Aug 2008 09:25:27 +0200
Delivered-to: mailing list perl6-all@perl.org
Delivered-to: perl6-all-poster@perl.org
Delivered-to: mailing list perl6-language@perl.org
Delivered-to: perl6-language@perl.org
In-reply-to: <CFBAD7E0F94940BB8B273497680BAEB9@deltatronic>
List-help: <mailto:perl6-all-help@perl.org>
List-id: <perl6-all.perl.org>
List-id: <perl6-language.perl.org>
List-post: <mailto:perl6-all@perl.org>
List-subscribe: <mailto:perl6-all-subscribe@perl.org>
List-unsubscribe: <mailto:perl6-all-unsubscribe@perl.org>
Mailing-list: contact perl6-all-help@perl.org; run by ezmlm
References: <31238-20726@sneakemail.com> <200808111954.41804.thomas@sandlass.de> <CFBAD7E0F94940BB8B273497680BAEB9@deltatronic>
HaloO,

Michael Mangelsdorf wrote:
Actually I can even imagine allowing almost all chars
in the middle of identifiers.

Is this a trend we should extrapolate into the lifetime scope
of the Perl 6 language?
How far are we in this process, given Unicode guillemets for hyper ops?

Is this supposed to be a joke or a serious contribution to the
discussion? Mine was serious in the sense that I consider the
enforcement of whitespace for infix ops a good thing or at least
not a bad side-effect. What's so different in $foo-bar versus
$foo*bar, $foo+bar or $foo/bar? The latter might e.g. indicate
path variables. Or imagine a coding convention where junctive
variables bear their generating operator: $foo|bar, $foo&bar and
$foo^bar.


Regards, TSa.
--

"The unavoidable price of reliability is simplicity" -- C.A.R. Hoare
"Simplicity does not precede complexity, but follows it." -- A.J. Perlis
1 + 2 + 3 + 4 + ... = -1/12  -- Srinivasa Ramanujan


<Prev in Thread] Current Thread [Next in Thread>