Karl Lehenbauer

I updated the flightaware fork of tsp's tclparser to TEA 3.9 and issued https://github.com/tpoindex/tsp/pull/10 back to this repo. If this has fixed the problem, please close this issue. Thanks.

It's running /sbin/md5 instead of doing whatever it's supposed to do.

The problem is due to some interaction between critcl, up to and including 3.1.15, and tclreadline. If in my .tclshrc I don't require tclreadline then the problem doesn't happen. I'm...

That's a good point. If the proc arguments were kept in the normal style instead of adding the "returning" thing I was proposing but it still had the additional section...

Also getting forward declaration warnings for Tcl_PushCallFrame and Tcl_PopCallFrame. Their names seem to indicate they should be defined in tcl.h, but they are defined in tclIntDecls.h.

https://github.com/flightaware/tsp_examples

This compiles and works if the upvar target, var, is defined as a var instead of a boolean and a separate boolean var is used... ``` tcl #tsp::var var #tsp::boolean...

Perhaps tsp should be using Tcl_UpVar to link a local obj to the correct frame and variable?

A sample bladeRF config file as a result of running calibration might be: ``` set lnagain 6 set txvga1 -35 set txvga2 0 set rxvga1 30 set rxvga2 0 cal...

Agreed, this would be very difficult to achieve and would affect non-shared-memory speedtables performance negatively, about for sure. The atomicity issue Peter brought up could be solved with locks, but...