On Wed, Nov 24, 2004 at 09:45:27AM -0500, Ken Fox wrote: > As long as an architecture change is on the > table, might as well make it a doozy.
Quite a lot of us would just like parrot COMPLETE and CORRECT before starting to put a lot of effort into how fast it is. PLEASE can we get parrot functionally complete, THEN start refactoring it to go faster. Until such time as we have complete, functional high level language running on it, with real world programs (rather than benchmarks and torture tests) optimisations are likely to be premature, as we don't have complete or realistic data of what our true speed problems are. ONLY when we have a real language complete and running (and yes, 100% of python running seems to be the easiest one here) do I feel that we'll actually be justified in spending time and effort undoing things that work (albeit slowly) and redoing them. Currently we keep liking to generate a lot of heat (and little light) redoing things that are currently too slow, which I have NO DOUBT that we're going to want to re-redo later in the light of real data. Nicholas Clark
