Re: Namespaces (At Long Last)

2005-12-04 Thread Leopold Toetsch
On Dec 4, 2005, at 5:57, Matt Diephouse wrote: Roger Browne <[EMAIL PROTECTED]> wrote: Leopold Toetsch wrote: add_sub($S0, $P0) add_namespace($S0, $P0) add_var($S0, $P0) Which HLLs would use these interfaces? Maybe I'm missing the point, but I see these being used in th

starting to release - no svn cis please

2005-12-04 Thread Leopold Toetsch
Please no further svn checkins, until the release announce is out. Thanks, leo

Parrot 0.4.0 "Luthor" Released!

2005-12-04 Thread Leopold Toetsch
On behalf of the Parrot team I'm proud to announce another major release of Parrot. More than 530 svn checkins and 1000 added tests by numerous folks bump up the version to 0.4.0. I'd like to thank all involved people as well as our sponsors for supporting us. What is Parrot? Parrot is a virtual

release 0.4.0 done

2005-12-04 Thread Leopold Toetsch
* svn ci is fine again - may the hacking continue * a few 'make testr' (run test via .pbc) tests are broken, at least one due to an expected compile error in the test, which then doesn't create the test file of course. I didn't find the time[1] to look more closely into other failures. Thanks

Re: Namespaces (At Long Last)

2005-12-04 Thread Matt Fowles
Leo~ On 12/4/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > > On Dec 4, 2005, at 5:57, Matt Diephouse wrote: > > > Roger Browne <[EMAIL PROTECTED]> wrote: > >> Leopold Toetsch wrote: > >> > add_sub($S0, $P0) > >>> > add_namespace($S0, $P0) > >>> > add_var($S0, $P0) > >

some goals for the next release

2005-12-04 Thread Leopold Toetsch
This is an unordered collection of my thoughts towards a next release: * namespaces: create a PDD based on Matt's document * interfaces: start some brainstorming, what we might need in Parrot core * bytecode & library loading: needs rewriting and major cleanup * config module cleanup: auto/jit.

scalar/array contexts in perl5 vs. perl6

2005-12-04 Thread Mike Li
what is a good translation of the following C into perl6? #include void print(int y[]) { int ii; for (ii = 0; 9 > ii; ++ii) { printf("%d ", y[ii]); } printf("\n"); } int main() { int x = 0; int y[] = {1, 2, 3, 4, 5, 6, 7, 8, 9}; y[x++]++; /* line that matters */ p

Re: some goals for the next release

2005-12-04 Thread Roger Browne
> Something else? I would be pleased to have a design decision made regarding inheritance of attributes in Parrot objects. See the last few comments here: https://rt.perl.org/rt3/Ticket/Display.html?id=36411 for the design questions that arose. Regards, Roger Browne

Re: scalar/array contexts in perl5 vs. perl6

2005-12-04 Thread Juerd
Mike Li skribis 2005-12-04 13:10 (-0500): > in perl5, i would've written something like: > my $x = 0; my @y = 1..9; @y[$x++]++; print "$x\n"; print "@y\n" > but in perl6, the '@' sigil always means list context, so should i > write the following? > my $x = 0; my @y = 1..9; [EMAIL PROTECTED]

Re: scalar/array contexts in perl5 vs. perl6

2005-12-04 Thread Sam Vilain
On Sun, 2005-12-04 at 13:10 -0500, Mike Li wrote: > what is a good translation of the following C into perl6? > [...] >int x = 0; int y[] = {1, 2, 3, 4, 5, 6, 7, 8, 9}; y[x++]++; /* line > that matters */ [...] > > > in perl5, i would've written something like: > > my $x = 0; my @y = 1..9

Re: Namespaces (At Long Last)

2005-12-04 Thread Bob Rogers
From: Matt Fowles <[EMAIL PROTECTED]> Date: Sun, 4 Dec 2005 12:35:24 -0500 . . . On 12/4/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > > . . . Which HLLs are able to > divide their symbols into above categories? . . . > > Remaining for me is the distiction between a

Re: Namespaces (At Long Last)

2005-12-04 Thread Matt Diephouse
Leopold Toetsch <[EMAIL PROTECTED]> wrote: > And it doesn't answer my question at all, sorry. Which HLLs are able to > divide their symbols into above categories? Further: as this proposals > deals with the managment of namespaces, a special typed interface for a > 'namespace' symbol name seems not

Flunking tests and failing code

2005-12-04 Thread Gaal Yahas
There's a bikeshedding question of some visibility: now that we have a C builtin, what do we do with C? There's plenty of code out there that uses fail as an exported function from pugs' Test.pm or Perl 5 testing modules. We want to keep Test primitives exported and fun to use, to encourage people

the $! too global

2005-12-04 Thread Darren Duncan
I've run into a problem today with my Perl 6 coding, which is due to a perceived design flaw in the current Perl 6 spec (this was discussed on #perl6 just now, mainly between myself and autrijus), so I'm bringing it up here. And yes, autrijus thinks the behaviour I'm seeing in Pugs is accordi

Re: Flunking tests and failing code

2005-12-04 Thread Luke Palmer
On 12/5/05, Gaal Yahas <[EMAIL PROTECTED]> wrote: > There's a bikeshedding question of some visibility: now that we have a > C builtin, what do we do with C? Is it possible to do nothing with it? That is, can we coerce the Test module to understand when the main program "fail"s? This may be prob