On Feb 26, 2010, at 12:24 PM, Kobi Lurie wrote: > - improve debugging in the ide, so that the walker walks the written > code and not the inlined representation. > - better error reporting - when possible, try to pinpoint the exact > problem. for example, if there is a circular dependency let the user > know which vocabs responsible and which words create the situation.
I agree that error reporting and debugger improvements would be great projects, Kobi. In fact, I'm in the middle of writing those up as project ideas. If you have anything to add to my proposals once they're up on the wiki, feel free to add to them. > - a contracts framework as a vocabulary. I think it's good but have no > real use cases to prove. Checks inputs and outputs with (excessive) > predicates when debug is on, > and raises an error to show in-between which words this contract failed. Sounds good. This is possible right now using the "typed" library and predicate classes, but a more formalized contract library with the option of stripping out assertions at deploy time could be useful. > - allow marking a word safe or unsafe. all the words that use an unsafe > word would become unsafe themselves, unless explicitly marked safe. > - allow marking a word as pure, that is, no side effects, so > optimizations like merging subsequent maps into one are possible in this > context. These both seem like valid project ideas. But be warned that while "pure" makes loop fusion theoretically possible, it doesn't necessarily make it easy to implement. -Joe ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
