[snip]
> > PS: But before reinventing a wheel, i would like to suggest to
> > adopt the .NET/Java object hierarchy.
>
> uhm. either I am completely wrong or you are totally out
> of track. I really don't understand what you're talking about :-)
Urgs. Hopefully i didn't trapped into a dunghill ?
[snip]
> effort on properties), so I started to put down a tentative
> class hierarchy of the Perl6 language (I call it P6FC for
> Perl6 Foundation Classes, but the name may (should? :-) very
> well change).
A very good idea, but i am afraid that this ML isnt the right
audience.
PS: But befor
> to provide a feeling for the weight of opinion, e.g., "most
> people felt this way", "some people felt differently", etc.
One should trace back who was of what opinion. So my suggestion would be
Discussion: "Foo feature"
"Want it":Person A, Person B, Person C, Person D
"Reject it:
Thats a great idea.
Murat
> > Apocalypse 6 and Exgenesis 6. Please do a search on
> perl.com for 1-5.
> s/en//
>
> Exegesis \Ex`e*ge"sis\, n.; pl. Exegeses. [NL., fr.Gr. ?,fr. ?
>to explain, interpret; ? out + ? to guide, lead, akin, to ?
>to lead. See Agent.]
>1. Exposition; explanation;
> It is likely that I will start reading again after A6 and E6
Sorry for uninformedness, but what is "A6" and "E6" ? Any versioning of
p6 dev releases ?
Murat
> Strange. I think parameters to subroutines are in list
> context unless stated otherwise.
>
> -Scott
I agree. Do we miss something ?
Murat
> or as useful as:
>
>my DNA %sequence is human size(4) =
>(alpha => 'atgc', beta => 'ctga', gamma => 'aatt',
> delta => 'ccaa'_;
oh , this is damn *PERFECT* !
a) easy reading
b) 'type' and 'property' adjacent without hopping through list
of varnames or complex prope
> 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, $ga
> Why should you care? Perl 6 isn't going to be that strictly
> typed, is it?
Not even optional ?
Murat
> Properties *can* be smart-matched:
>
> print "creditcard" if $var.prop().{CreditCard} ~~ 'VISA';
> or:
> print "creditcard" if $var.prop{CreditCard} ~~ 'VISA';
> or:
> print "creditcard" if $var.CreditCard ~~ 'VISA';
>
> Damian
>
I think this is similar to "John Williams" su
> Yes, but
>
> my int $foo is constant;
>
> Is self-explanatory for many language-speakers. If I recall,
> the set of cross-language-programmers is a proper subset of
> the set of language-speakers. It is clear which is clearer :).
You do "proof by best case scenario". In my previous posti
> > where the distance grows with property-syntax-complexity.
>
> Oh, *that's* what you're concerned about?
> Then you're just not thinking in enough simultaneous dimensions:
>
>
> my int ($pre, $in, $post) is constant
> = (0,1, 2);
This could been written faster i
> my $var = 0;
> # or my $var = "0";
> # or my int $var = 0;
> # or my num $var = 0;
>
> # all 4 cases should print "is integer"
> print "is integer" if int $var == $var;
>
> This should work as a more generic method to test Integer
> *value*, rather than type, which IMHO is more useful (and
>
> > In the above case int($var) == $var returns true when I
> would want it
> > to return false.
>
> print "date" if $var.isa(int);
> print "date" if isa $var: int;
> print "date" if $var ~~ int;
>
> Those should all work. IMO the first reads the best. That
> will also work for C
> > It's also far slower. Constructing a 31-element list, junctionizing
> > it,
>
> This might well be done at compile-time. And/or, lazily. So
> the cost of these two steps is likely to be negligible.
>
> > then testing against each element vs. 2 numeric comparisons.
>
> Yes. That's a signifi
> > my int ($pre, $in, $post) is constant = (0..2);
> >
> > Two things "type and property" that belong so together
>
> Do they? Surely the type and constancy of a variable are
> entirely orthogonal to each other.
Oh yes. Psycho-affectivly it is disturbing seeing the group of variables
($pre, $
In the name of the bum (and c++-used eyes), i have some small criticism
about the "type and property" syntax. "Exegesis 2 - Any variables to
declare?" suggests:
my int ($pre, $in, $post) is constant = (0..2);
Two things "type and property" that belong so together are visually so
disrupted, which
I have an idea !
Damian conway's Attribute::Types suggests
"my $date: INTEGER(1..31);"
but i think
"my int( 1..31 ) $date"
is more like a c++/java
"Integer date( 1, 31 );"
and a weddig of both should fit perl6 best. Would mean:
my int( 1..31 ) $var;
$date = 23; # okay
$date
19 matches
Mail list logo
