Re: Guidelines for internals proposals and documentation

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 keep
external
 > API
 > >design separate from internal design I think we'll have more wiggle
room
 > >to experiment. (That's one of the big problems with perl 5 right now.)
 > 
 > That's one of the reasons I'd like to work on the APIs first. I realize

 > that doing even that will have an effect on the design of the pieces
 > behind 
 > the APIs, but we have to startsomewhere.

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. Wouldn't we have to know the outside before we try to put the
insides together? Is there any action on the api lists that I'm not
seeing? If not, I'd say we've got the cart before the horse.