Christian Soeller wrote: > What Karl was trying to get at is a suggestion to have one RFC on > indexing instead of three competing ones, for example. The current > approach seems to be make a new RFC always (regardless what is there > already). The other approach would be to take existing ones and rewrite > them heavily. > > Christian Yes. And for the record I also think the current approach of lets generate ten million RFCs and Uncle Larry knows best is nuts. There are already too many RFCs on this topic alone to grasp coherently. Karl
- Re: Proposed RFC for matrix indexing and slicing Dan Sugalski
- Re: Proposed RFC for matrix indexing and slicing Karl Glazebrook
- Re: Proposed RFC for matrix indexing and slicin... Dan Sugalski
- Access to the perl6 parser Jim Edwards
- Re: Access to the perl6 parser Dan Sugalski
- Re: Access to the perl6 parser Jim Edwards
- Re: Access to the perl6 parser Dan Sugalski
- Re: Access to the perl6 parser Christian Soeller
- Re: Access to the perl6 parser Jim Edwards
- Re: Proposed RFC for matrix indexing and sl... Christian Soeller
- Re: Proposed RFC for matrix indexing an... Karl Glazebrook
- Re: Proposed RFC for matrix indexi... Nathan Torkington
- Re: Proposed RFC for matrix indexi... Karl Glazebrook
- Re: Proposed RFC for matrix indexi... Dan Sugalski
- Re: Proposed RFC for matrix indexi... Jeremy Howard
- Re: Proposed RFC for matrix indexi... Bart Lateur
- Re: Proposed RFC for matrix indexi... c . soeller
- Re: Proposed RFC for matrix indexi... Karl Glazebrook
- Re: Proposed RFC for matrix indexi... Nathan Torkington
- Re: Proposed RFC for matrix indexi... Karl Glazebrook
- Re: Proposed RFC for matrix indexi... Larry Wall