On Wed, 14 Aug 2002 15:40:35 -0600 (MDT), Luke Palmer wrote:
> We could make arglists exactly equivilent to the way they're done in Perl 5,
> which is a good way.
>
> sub foo($a, $b, *@c) {...}
>
> Would be exactly equivilent to Perl 5's
>
> sub foo { my ($a, $b, @c) = @_; ... }
>
> Si
and this just jumped out at me:
class Foo {
private string|int bar;
static create(string|int newBar) {
bar = newBar;
}
}
In other words, as I understand it, you can type the variable bar as
either an int or a string.
Aside from simply, "my $bar;", w
Chris Dutton wrote:
> and this just jumped out at me:
>
> class Foo {
> private string|int bar;
> static create(string|int newBar) {
> bar = newBar;
> }
> }
>
> In other words, as I understand it, you can type the variable bar as
> either an int or a string.
>
> Aside
At 4:03 PM -0400 8/13/02, Mike Lambert wrote:
> > In essence, all Perl 5 functions have a signature of (*@_ is rw).
>> Perhaps the translator can turn some of those into (*@_). What'd
>> really be cool is if it could pick up an initial
>>
>> my ($a, $b, $c) = @_;
>
>Excuse my ignorance he
> Well, I'm still hopeful Larry will approve superpositions. In which case,
> since types in Perl 6 are first-class, you would be able to write
> the same thing something like:
>
>
> class Foo {
> attr any(str,int) $bar;
>
> method SETUP(any(str,int) $newBar) {
On Fri, 16 August 2002, Luke Palmer wrote:
> I want superpositions too :). But, what would this mean?
>
> my all(str, int) $foo;
> #...
That you need some *serious* psychotherapy! ;-)
Actually, it would mean that $foo can only contain values
whose type is simultaneously C and C.
On Sat, Aug 17, 2002 at 06:41:02AM +1000, Damian Conway wrote:
> Well, I'm still hopeful Larry will approve superpositions. In which case,
> since types in Perl 6 are first-class, you would be able to write
> the same thing something like:
>
>
> class Foo {
> attr any(str,int
On Fri, 2002-08-16 at 19:05, [EMAIL PROTECTED] wrote:
> On Fri, 16 August 2002, Luke Palmer wrote:
>
> > I want superpositions too :). But, what would this mean?
> >
> > my all(str, int) $foo;
> > #...
>
> That you need some *serious* psychotherapy! ;-)
>
> Actually, it would mean tha
ive oft wondered how a constant/parameter namespace could be designed to:
- lighten Exporter symbol export in perl 5
- expose (for example) POSIX constants in only the contexts where
theyre meaningful
within a POSIX call - ex various c-open flags (im too lazy
to cite any cu
