Based on the discussion of "Factoring that's worth it" I thought a good way to "prototype" a proposed alternative and have a way to measure if its effect would be to take the worst over/keep offender and try to reduce it.
If you look at extra/ogg/player/player.factor it is full of repetitive over and keep usage. Either this is because it wasn't written in the best way and could be improved with existing Factor words, OR new words with a stack effect that doesn't require over and keep works better. For me this would be very instructive to see how someone familiar with Factor would go about refactoring this with existing words to not need over and keep. If it can't be done then I'd also be interested in how new words could improve things. That sound like a good idea to anyone else? No offense to you Chris on the code, it's just the one with the most usage and would be a good test case. -- Zed A. Shaw - Hate: http://savingtheinternetwithhate.com/ - Good: http://www.zedshaw.com/ - Evil: http://yearofevil.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
