Hello,
I'm having a seriously good time porting Maypole to Perl 6. If you
still have reservations about how Perl 6 is going to be to program in,
I urge you to try programming in it.
Now, commercial over, I have some questions.
What's the syntax for declaring inherited anonymous classe
Hi,
Simon Cozens wrote:
> I'm having a seriously good time porting Maypole to Perl 6. If you
> still have reservations about how Perl 6 is going to be to program in,
> I urge you to try programming in it.
> Now, commercial over, I have some questions.
:)
> class Foo {
> has Cla
Hi,
Yuval Kogman wrote:
> We have a pretty complex declarative language for argument
> processing in the parameter declaration:
[...]
> arity as a number does not give enough reflection into these
> properties.
Indeed.
> Are signatures going to be an exposed first class object in Perl 6?
I hope
Hi,
while responding to nothingmuch++'s post "function signatures?", I
thought that it'll be great if Code objects were fully introspectable.
I.e.:
&foo.statements; # List of statements
&foo.statements[0] # First statement
&foo.statements[2] = ...;# Statement modif
[EMAIL PROTECTED] (Ingo Blechschmidt) writes:
> I think the only thing you're missing are two braces:
> $.request_class = class is Foo::Request {};
Thank you; then how do I put methods into $.request_class?
--
"I will make no bargains with terrorist hardware."
-- Peter da Silva
Hi,
Simon Cozens wrote:
> [EMAIL PROTECTED] (Ingo Blechschmidt) writes:
>> I think the only thing you're missing are two braces:
>> $.request_class = class is Foo::Request {};
>
> Thank you; then how do I put methods into $.request_class?
$.request_class = class is Foo::Request {
method
On May 26, Patrick R. Michaud said:
N backtracking fails completely
N remove what matched up to this point from the
string
N we must be after the pattern P
N we must NOT be after the pattern P
N we must be before the
On 5/29/05, Ingo Blechschmidt <[EMAIL PROTECTED]> wrote:
> Hi,
>
> while responding to nothingmuch++'s post "function signatures?", I
> thought that it'll be great if Code objects were fully introspectable.
>
> I.e.:
> &foo.statements; # List of statements
> &foo.statements[0]
Ingo Blechschmidt wrote:
Are signatures going to be an exposed first class object in Perl 6?
I hope so, too.
~&foo.signature;
# Signature objects should stringify to a canonized form, e.g.:
# ~sub (Str $bar, CoolClass $z where {...}) {...}.signature ==>
# 'Str $bar, ANONCLASS(0xDEADBEEF)
[This is a repost, somehow it didn't get through before, sorry.]
Luke wrote:
> Both transparent dereferencing (infinite $$foo) and
> opaque dereferencing (one-level $$foo) have their uses, but they are
> definitely distinct.
Well, they are more like variations on a theme.
> Instead of adding d
10 matches
Mail list logo
