Murat Ünalan wrote:
And that shows precisely why Perl 6 does it the other way.
Prepending extended properties like that makes the
declaration almost unreadable. Because it separates the
I shoot in my own foot. My example was extremly bad. Give me a better
try:
(1)
my size(4), human DNA ($alpha, $beta, $gamma, $delta ) = ( 'atgc',
'ctga', 'aatt', 'ccaa' );
is so perfect, vs
(2)
my DNA ($alpha, $beta, $gamma, $delta) is human, size(4) = ( 'atgc',
'ctga', 'aatt', 'ccaa' );
which is so prone to overlook the "eucaryotic" property during i.e.
debugging hassle. Why do code beautify (2) when (1) so crystal clear
without it.
Because (1) *isn't* crystal clear. At least, not to me. And certainly
not as readable as:
my DNA ($alpha, $beta, $gamma, $delta) is human size(4)
= ('atgc', 'ctga', 'aatt', 'ccaa');
or as useful as:
my DNA %sequence is human size(4) =
(alpha => 'atgc', beta => 'ctga', gamma => 'aatt', delta => 'ccaa'_;
And (1) is so close to natural language.
Perhaps to *your* natural language, but not to mine. :-)
And that's what it may come down to. Perhaps we just have to agree
to disagree on this question. You're not convincing me at all, and
I'm obviously not convincing you either.
BTW: are multiple properties separated with ',' ?
No. Whitespace or an C<is>.
Damian
