Re: Guidelines for internals proposals and documentation

2000-11-21 Thread Dan Sugalski
At 02:45 PM 11/17/00 +, David Grove wrote: Dan Sugalski [EMAIL PROTECTED] wrote: At 10:19 AM 11/17/00 -0800, Ken Fox wrote: However, I don't want to see early (premature) adoption of fundamental pieces like the VM or parser. It makes sense to me to explore many possible

Re: Guidelines for internals proposals and documentation

2000-11-17 Thread Dan Sugalski
At 10:19 AM 11/17/00 -0800, Ken Fox wrote: However, I don't want to see early (premature) adoption of fundamental pieces like the VM or parser. It makes sense to me to explore many possible designs and pick and choose between them. Also, if we can keep external API design separate from internal

Re: Guidelines for internals proposals and documentation

2000-11-17 Thread David Grove
Dan Sugalski [EMAIL PROTECTED] wrote: At 10:19 AM 11/17/00 -0800, Ken Fox wrote: However, I don't want to see early (premature) adoption of fundamental pieces like the VM or parser. It makes sense to me to explore many possible designs and pick and choose between them. Also, if we can

Re: Guidelines for internals proposals and documentation

2000-11-17 Thread John van V
"David Grove" [EMAIL PROTECTED] wrote : But.. but... but... we don't even have a design spec. I mean, we don't even know for sure what Perl 6 is going to look like for certain, inside or outside. This is precisely why I proposed the BS level just below Development. In fact I'm going to

Re: Guidelines for internals proposals and documentation

2000-11-15 Thread John van V
Using the IBM article that Jarkko found as an example, core implementations of different languages may have more in common with each other than implemetations of the same language, I think PPC is actually significant enough so that it should not be painted into a perl-only corner. Seeing

Re: Guidelines for internals proposals and documentation

2000-11-15 Thread Adam Turoff
On Wed, Nov 15, 2000 at 04:20:58PM -0500, Dan Sugalski wrote: I want perl 6's internal API to have the same sort of artistic integrity that the language has. That's not, unfortunately, possible with everyone having equal say. I'd like it to be otherwise, but that's just not possible with

Re: Guidelines for internals proposals and documentation

2000-11-15 Thread David Grove
Nat and I argued parts of this (I think this is included) at some length. Actually, I think I drove him crazy getting specifics out of this. Adam Turoff [EMAIL PROTECTED] wrote: On Tue, Nov 14, 2000 at 05:59:40PM -0500, Dan Sugalski wrote: 6) Only a WG chair, pumpking, or one of the

Re: Guidelines for internals proposals and documentation

2000-11-15 Thread Nicholas Clark
On Wed, Nov 15, 2000 at 11:35:56AM -0500, Adam Turoff wrote: On Tue, Nov 14, 2000 at 05:59:40PM -0500, Dan Sugalski wrote: 6) Only a WG chair, pumpking, or one of the principals (i.e. Me, Nat, or Larry, or our replacements) can mark a PDD as developing, standard, or superceded. This