tsp
tsp copied to clipboard
tpoindex
Tcl Static Prime
On FreeBSD 10 in lib/tclparser-1.4.1 configure crashes: ``` checking for correct TEA configuration... ok (TEA 3.2) checking for Tcl configuration... found /usr/local/lib/tcl8.6/tclConfig.sh checking for existence of /usr/local/lib/tcl8.6/tclConfig.sh... loading ... checking...
If I run, like, "tclsh latlons.tcl", it works, but if I start Tcl interactively and do a "source latlons.tcl", I get some MD5 signatures output to the terminal and a...
An idea for your consideration... Instead of hinting the compiler with comments how about if the same hinting is formally available through tsp::proc itself? If compilation fails tsp::proc can still...
TSP_Util_string_compare_const was forward-declared in TSP_util.c. A trivial reordering declares the function before its first call. clang on FreeBSD was warning about forward definitions for srand48 and drand48 and this fixes...
- Update tclparser TEA tclconfig/\* files from 3.2 to 3.9. - make tclparser "make distclean" also delete the autom4te.cache directory. - regenerate configure script - create a .gitignore to tell...
I presume the code below coredumps because tsp upvar accepts but doesn't support #0. Would this be hard to add? We call the routine below a lot and avoid running...
Currently tsp cannot compile something like ``` tcl set bool [info exists flightplan(orig)] ``` It apparently does support ``` tcl set want "orig" set bool [info exists "flightplan($want)"] ``` ...but...
tsp seems to reject setting or accessing global variables when they are referenced using the double-colon (global namespace) syntax. If they are accessed by declaring them with the "global" command...
At the bottom of https://github.com/tpoindex/tsp/blob/master/docs/runtime.md, this section reads "TSP compiled procs are not thread safe, so use of Tcl thread package must be avoided when invoking TSP compiled procs." Since...