Re: New Todo
On Wed, Jan 30, 2002 at 07:48:25AM +0100, Paul Johnson wrote: On Tue, Jan 29, 2002 at 09:57:16PM +, Simon Cozens wrote: I've started a new TODO list. Remind me of anything else that needs doing; Sandboxes. Has anyone given any thought as to whether Parrot should support use Safe, and if so, how? And remember that Safe is built on ops (ops.pm etc) and ops is very useful in it's own right (eg for allowing limited perl ops in a config file). Tim.
Re: New Todo
At 11:06 AM + 1/30/02, Tim Bunce wrote: On Wed, Jan 30, 2002 at 07:48:25AM +0100, Paul Johnson wrote: On Tue, Jan 29, 2002 at 09:57:16PM +, Simon Cozens wrote: I've started a new TODO list. Remind me of anything else that needs doing; Sandboxes. Has anyone given any thought as to whether Parrot should support use Safe, and if so, how? And remember that Safe is built on ops (ops.pm etc) and ops is very useful in it's own right (eg for allowing limited perl ops in a config file). And our safe interpreter will use the same sort of mechanism. (Though you won't necessarily be able to do that from within a safe interpreter. Some stuff won't be overridable, but that's fine. -- Dan --it's like this--- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
Re: New Todo
Any idea what of this will become 0.0.4?
Re: New Todo
On Wed, 30 Jan 2002, Steve Fink wrote: Any idea what of this will become 0.0.4? Is there any chance someone (simon) could make a TODO_FIRST [1], which contains the goals for our next point release. I'm far too lazy to search through mailing list archives to find it every time I want it. [1] or TODO_NOW or TO_REALLY_DO or JFDI or something. Alex Gough
Re: New Todo
On Wed, Jan 30, 2002 at 08:39:17PM +, Alex Gough wrote: On Wed, 30 Jan 2002, Steve Fink wrote: Any idea what of this will become 0.0.4? Is there any chance someone (simon) could make a TODO_FIRST [1], which contains the goals for our next point release. I'm far too lazy to search through mailing list archives to find it every time I want it. [1] or TODO_NOW or TO_REALLY_DO or JFDI or something. Perhaps a target version for each item? [0.0.4] collision resolution in hashtables [0.0.5] PMC attributes [future] translate Larry's brain to parrot opcodes
Re: New Todo
On Wed, Jan 30, 2002 at 10:01:50PM +, Simon Cozens wrote: begin quote from Steve Fink: Perhaps a target version for each item? Oh, bother. This is the second time I've been asked about this, so I suspect that my goals for the forthcoming releases aren't amazingly clear. Or perhaps people lose track of your last pronouncement over time. Rather than periodically resending it to the list, might I suggest checking it into CVS? TODO sounds like a nice filename for it. :-)
Re: New Todo
On Tue, Jan 29, 2002 at 09:57:16PM +, Simon Cozens wrote: JIT --- More instructions needed! Register my vote for some introductory documentation. docs/jit.pod is good for someone who already knows how the JIT works, but I'd like something for idiots like me who just want to know what we can expect to work. To me, the -j flag means go really fast. Or just hang. Or maybe crash, and I don't know when to expect which.
Re: New Todo
On Tue, Jan 29, 2002 at 09:57:16PM +, Simon Cozens wrote: I've started a new TODO list. Remind me of anything else that needs doing; Sandboxes. Has anyone given any thought as to whether Parrot should support use Safe, and if so, how? -- Paul Johnson - [EMAIL PROTECTED] http://www.pjcj.net
