Joshua Gatcomb wrote:
We haven't had a new release since Feb 29th.
Yep. The Plan was to do a release in June. Pie-thon did interfer.
Since the usual purpose of a point release is to have
features finished and bugs squashed, it may be a good
time for another release.
I'd say in a month or so.
leo
We haven't had a new release since Feb 29th.
From what I have seen from the various on-line forums,
newcomers aren't aware of the progress since then.
The latest round of discussion appears to have
resulted in the following guidelines from our fearless
leader:
1. Divorce internals from
') ; ## this is ok.
@l = (1 , 2 ) ; ## this is ok.
@l = (2) ; ## this is NOT ok.
Soo, when setting an array with ONE value doesn't work!
Also we can't set HASHes yet!
I think that now is time to add syntax to Perl6, since parrot has resources
for that now.
Tested in parrot-0.1.0 (last release
what is the problem but I
think it's related to threads.
It's Debian 3.0 on parisc using gcc 3.0.4
Any idea how to solve it?
Provide more informatiion?
$ cat myconfig
Summary of my parrot 0.1.0 configuration:
configdate='Wed Mar 3 12:56:25 2004'
Platform:
osname=HPUX, archname=PA
Daniel Grunblatt [EMAIL PROTECTED] wrote:
$ cat myconfig
Nothing special here AFAIK.
spe170 gdb parrot
When it hangs:
- run parrot in one console
- open a 2nd console
- get the pid(s) of parrot
$ ps -C parrot
- start debugger
$ gdb parrot the_pid
$ bt
Breakpoint 1, pmc_init_null
When updating the old version I had at the TD machine to the current cvs
version I realize that it fails right after start running, entering in an
eternal loop, I could not find out exactly what is the problem but I think
it's related to threads.
It's Debian 3.0 on parisc using gcc 3.0.4
Any
Daniel Grunblatt [EMAIL PROTECTED] wrote:
When updating the old version I had at the TD machine to the current cvs
version I realize that it fails right after start running, entering in an
eternal loop, I could not find out exactly what is the problem but I think
it's related to threads.
It's
Parrot 0.1.0 Leaping Kakapo Released!
The Parrot team proudly presents the Parrot 0.1.0 leap release. It
provides some milestones like objects and multi-threading1[1] and
supports many more platforms.
After some pause you can grab it from
http://www.cpan.org/authors/id/L/LT/LTOETSCH/parrot-0.1.0
Benjamin Goldberg [EMAIL PROTECTED] wrote:
Allow .macro in imcc, for when we're parsing pir code.
This is already enabled.
Macro-ize the stub functions in default.pmc, so that throwing an
exception takes one line of C code.
Yep. And autogenerate these from vtable.tbl if default.pmc has no
Steve Fink wrote:
In light of the insane amount of work that's gone into Parrot
recently, I'd say it's about time to cut another release. What else
would people like to slip in? This is not a freeze announcement yet --
I want to know what people think of the state of things they're
working
Steve Fink writes:
In light of the insane amount of work that's gone into Parrot
recently, I'd say it's about time to cut another release. What else
would people like to slip in? This is not a freeze announcement yet --
I want to know what people think of the state of things they're
working
-- Dan, if it's ok with you, I'd like to
call this 0.1. Leo's got some form of exceptions in, which was the
stated gate to 0.1, and with the EXEC stuff and a real live Python
port, it seems to me that it's more than earned the name.
0.1.0 sounds right for me.
leo
On Feb-25, Leon Brocard wrote:
David sent the following bits through the ether:
Thanks. I better upgrade my version, I'm not seeing it in 0.0.9.
It's been a while since 0.0.9 (errr, 20th Dec). A lot has changed
since then. Maybe it's time for a 0.1.0 release. What are we waiting
David sent the following bits through the ether:
Thanks. I better upgrade my version, I'm not seeing it in 0.0.9.
It's been a while since 0.0.9 (errr, 20th Dec). A lot has changed
since then. Maybe it's time for a 0.1.0 release. What are we waiting
for? And why do we have so many version
Leon Brocard wrote:
It's been a while since 0.0.9 (errr, 20th Dec). A lot has changed
since then. Maybe it's time for a 0.1.0 release. What are we waiting
for?
Dan said: either exceptions or objects. Once we have one, we'll go to
0.1.0, and when the second will be implemented (order does
On Tue, 25 Feb 2003, Jerome Quelin wrote:
I want to include concurrent-funge support.
I'm not even going to ask :-)
Simon
At 4:52 PM + 2/25/03, Leon Brocard wrote:
David sent the following bits through the ether:
Thanks. I better upgrade my version, I'm not seeing it in 0.0.9.
It's been a while since 0.0.9 (errr, 20th Dec). A lot has changed
since then. Maybe it's time for a 0.1.0 release. What are we waiting
Dan Sugalski sent the following bits through the ether:
While I'll call C many things (not all of them repeatable) I'm not
sure toy is one of them. Nor Forth, Fortran, APL, COBOL, Lisp, or
Basic... :)
Granted, but those aren't the languages we're interested in. Parrot is
for dynamic
Jerome Quelin [EMAIL PROTECTED] writes:
And even toy languages may benefit from objects (yes, I really need
objects in order to implement -98 version of Befunge, especially
since I want to include concurrent-funge support). Well, I could use
my own hand-crafted objects as a list of whatever,
interpreter now uses a list of lists (perlarray of
perlarrays to be more precise) instead of a list of strings.
I thought this big evolution needed a gap in my versioning scheme, so
this is now befunge 0.1.0 (instead of 0.07 - yes, I also went for a
traditional open-source versioning system
in my versioning scheme, so
this is now befunge 0.1.0 (instead of 0.07 - yes, I also went for a
traditional open-source versioning system)
Applied, thanks.
--
Dan
--it's like this---
Dan Sugalski
21 matches
Mail list logo
