diff options
| -rw-r--r-- | DEVELOPING | 5 | ||||
| -rw-r--r-- | TODO | 20 | ||||
| -rw-r--r-- | bench.tcl | 1 |
3 files changed, 3 insertions, 23 deletions
@@ -46,7 +46,7 @@ the project that is about to be started. The only thing that has to be taken care of is the project mode -- it should be "push mode". Once the project is created one must add a user that will actually -start commiting new files to the repo. It can also be done throught +start commiting new files to the repo. It can also be done through the WWW interface, so nothing more is necessary. Once finished with setting up a project on the WWW panel, one can @@ -88,7 +88,6 @@ submitting patches, you can verify that your changes didn't bring any regressions to the Jim. In order to do so, sample regression tests have been implemented. You can execute them by typing: - cd tests - make + make test All tests should succeed. @@ -15,32 +15,12 @@ OTHER COMMANDS NOT IN TCL BUT THAT SHOULD BE IN JIM EXTENSIONS -- OOP system - Cryptography: hash functions, block ciphers, strim ciphers, PRNGs. - Tuplespace extension (http://wiki.tcl.tk/3947) (using sqlite as backend) - Zlib - Gdlib - CGI (interface compatible with ncgi, but possibly written in C for speed) -SPEED OPTIMIZATIONS - -- Experiment with better ways to do literal sharing. - - * Currently literal sharing is completely removed. Can it be made - efficient? What is the cost vs. benefit? - -IMPLEMENTATION ISSUES - -- Objects lazy free. - -- Rewrite all the commands accepting a set of options to use Jim_GetEnum(). - - - Many have been done. - -- Every time an extension is loaded Jim should put the dlopen() (or win32 - equivalent) handle in a list inside the interpreter structure. When - the interpreter is freed all this handles should be closed with dlclose(). - REFERENCES SYSTEM - Unify ref/getref/setref/collect/finalize under an unique [ref] command. @@ -17,6 +17,7 @@ proc bench {title script} { set ts [string range $ts [expr {[string length $ts]-10}] end] if {!$batchmode} {puts "$Title -$ts ms per iteration"} } + catch { collect } } ### BUSY LOOP ################################################################## |