Objects and time
Dan Sugalski
ordering of classes for initialization and destruction in the face of
multiple inheritance. I'm doing the only sensible thing at the
moment--I'm actively ignoring it. I've burned a few hours chasing
down this rathole.
So, the question--shall we do objects and maybe miss the Feb 29th
release, or do the Feb 29th release and do objects for the next
release? As I think I'm only a little while off (maybe a day or so)
from getting it working, I'm tempted to take a miss on the nice date
in favor of a release with Good Stuff in it, but I'm flexible there.
Time to weigh in on it, though in this case the decision's up to the
Release Manager, so direct your on-list arguments to Leo. :)
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk
Leon Brocard
> So, the question--shall we do objects and maybe miss the Feb 29th
> release, or do the Feb 29th release and do objects for the next
> release?
Objects please!
Leon
--
Leon Brocard.............................http://www.astray.com/
scribot.................................http://www.scribot.com/
... That's Ren and Stimpy - they're way existential
Melvin Smith
>So, the question--shall we do objects and maybe miss the Feb 29th release,
>or do the Feb 29th release and do objects for the next release? As I think
>I'm only a little while off (maybe a day or so) from getting it working,
>I'm tempted to take a miss on the nice date in favor of a release with
>Good Stuff in it, but I'm flexible there.
Nice dates are amusing, but of no real use.
I say postpone the release.
-Melvin
Leopold Toetsch
> So, the question--shall we do objects and maybe miss the Feb 29th
> release, or do the Feb 29th release and do objects for the next
> release? As I think I'm only a little while off (maybe a day or so)
> from getting it working,
Don't post intermediate state, hack objects together ;) Objects are
missing since a long time and are announced still longer. So if possible
anyhow, please try to get it running.
WRT feature freeze: I'd say: Starting from Tue, 24th 8.00 GMT no more
feature patches *should* go in, *except* objects.
leo
Melvin Smith
>WRT feature freeze: I'd say: Starting from Tue, 24th 8.00 GMT no more
>feature patches *should* go in, *except* objects.
Basically that means: everyone will get really quiet and we will all watch
Dan. >:)
-Melvin
Simon Glover
Alternatively: everybody will spend their time writing tests and
documentation... (Well, OK, probably not, but I'm hopelessly optimistic).
Simon
Jonathan Worthington
----- Original Message -----
From: "Dan Sugalski" <d...@sidhe.org>
To: <perl6-i...@perl.org>
Sent: Monday, February 23, 2004 3:29 PM
Subject: Objects and time
> Okay, I've just trodden on one of the nasty bits of objects, proper
> ordering of classes for initialization and destruction in the face of
> multiple inheritance. I'm doing the only sensible thing at the
> moment--I'm actively ignoring it. I've burned a few hours chasing
> down this rathole.
>
> So, the question--shall we do objects and maybe miss the Feb 29th
> release, or do the Feb 29th release and do objects for the next
> release? As I think I'm only a little while off (maybe a day or so)
> from getting it working, I'm tempted to take a miss on the nice date
> in favor of a release with Good Stuff in it, but I'm flexible there.
>
> Time to weigh in on it, though in this case the decision's up to the
> Release Manager, so direct your on-list arguments to Leo. :)
>
Maybe we should go for a Feb 29th release, and then do objects for the next
release and call that 0.1. If 0.1 is going to be a milestone of sorts, I
feel the object stuff going in should be well documented and have tests and
examples. It'd also be good to have feedback from the various platforms
we'd like them to work on, and some time for people to toy with them a
little to spot any little quirks. If there's a push to get a release done,
I fear that may not happen. Of course, there may be no push to do a
release, in which case I don't object to holding off until it's really
ready.
Jonathan
Jens Rieks
Am Montag, 23. Februar 2004 17:09 schrieb Leopold Toetsch:
> WRT feature freeze: I'd say: Starting from Tue, 24th 8.00 GMT no more
> feature patches *should* go in, *except* objects.
can/should go the tetris example go in?
I'am writing documentation at the moment. Converting the example to use
parrot objects is my next plan.
> leo
jens
Leopold Toetsch
> Hi,
> Am Montag, 23. Februar 2004 17:09 schrieb Leopold Toetsch:
>> WRT feature freeze: I'd say: Starting from Tue, 24th 8.00 GMT no more
>> feature patches *should* go in, *except* objects.
> can/should go the tetris example go in?
If its running yes. I've to admit that I didn't test it. And examples
aren't that critical. They aren't really features :)
> I'am writing documentation at the moment. Converting the example to use
> parrot objects is my next plan.
Great.
> jens
leo
Tim Bunce
> Jens Rieks <par...@jensbeimsurfen.de> wrote:
> > Hi,
>
> > Am Montag, 23. Februar 2004 17:09 schrieb Leopold Toetsch:
> >> WRT feature freeze: I'd say: Starting from Tue, 24th 8.00 GMT no more
> >> feature patches *should* go in, *except* objects.
>
> > can/should go the tetris example go in?
>
> If its running yes. I've to admit that I didn't test it. And examples
> aren't that critical. They aren't really features :)
If you squint a little you could pretend they're tests :)
Tim.
Harry Jackson
> Dan Sugalski sent the following bits through the ether:
>
I would second that. I would prefer a cool release to a cool date ;-)
Harry Jackson