Re: Nested modules

2003-11-03 Thread Joseph Ryan
Luke Palmer wrote: So, we can have :: in names, but that doesn't represent any inherent relationship between the module before the :: and the one after. I think this is an important thing to keep. However, will it be possible to, for example, do: module Foo; module Bar { ... } And refer

How to get environment variables?

2003-11-03 Thread Andrew Shitov
Is it possible to get environment variables from perl6 programme? It failes when I try to use perl5 hash %ENV. Thanks.

Re: How to get environment variables?

2003-11-03 Thread Simon Cozens
[EMAIL PROTECTED] (Andrew Shitov) writes: Is it possible to get environment variables from perl6 programme? It failes when I try to use perl5 hash %ENV. Thanks. Are you sure you're using the Perl 6 hash syntax? (%ENV{FOO} rather than Perl 5-style $ENV{FOO}) What version of Perl 6 are you

Re: How to get environment variables?

2003-11-03 Thread Andrew Shitov
I tried this one-line programme for example: my %e = %ENV; and got this (parrot-0.0.13/perl are built under mandrake linux): Global '_HV_ENV' not found Error: '/parrot-0.0.13/parrot -r env.imc ' failed with exit code 1 Stopped at /parrot-0.0.13/languages/perl6/perl6 line 339

This week's summary

2003-11-03 Thread Piers Cawley
The Perl 6 Summary of the week ending 20031102 It's Monday morning, the croissants have been baked, the focaccia is glistening with all the extra virgin olive oil I poured on it as it left the oven and, in the airing cupboard, a raisin borodinsky slouches towards full proof

Re: Nested modules

2003-11-03 Thread Larry Wall
On Sun, Nov 02, 2003 at 07:50:05PM -0700, Luke Palmer wrote: : So, we can have :: in names, but that doesn't represent any inherent : relationship between the module before the :: and the one after. I : think this is an important thing to keep. : : However, will it be possible to, for example,

Re: Nested modules

2003-11-03 Thread Damian Conway
Larry wrote: In theory I suppose you could have objects with module attributes: class Foo { has module .Bar { ... } } Just don't ask me what it means... Of course, Larry's just joking there...he knows precisely what it means. It means that every object of class Foo has its own

Re: Nested modules

2003-11-03 Thread Joseph Ryan
Damian Conway wrote: Larry wrote: This kind of behaviour is more useful for nested classes, I suspect, but it should certainly be available for nested modules as well. So, what's the difference between a module and a class, and why would you want dynamic namespaces? Isn't that something you'd