4 ms·
Lisp compiles to native code, TCL is forever parsing the strings it passes around.
by lanstin 5y ago
Lisp compiles to native code, TCL is forever parsing the strings it passes around.
- kevin_thibedeau 5y ago> TCL is forever parsing the strings it passes around. No it isn't. Tcl has had dual-ported objects and a bytecode interpreter for over 20 years.
- lanstin 5y agoWell I learned something. But if you represent a list as a lift of strings wouldn’t it have to parse them as Argv in the c implementation? It has been a while but only 17 years since I wrote TCL commands but each one started with a list of strings. Maybe the byte code interpreter doesn’t work with older C extensions? But the main selling point of TCL was easy extension.
- pjmlp 5y agoOnly if you were using the pre-Tcl 8 FFI API, our startup was built on a Tcl "Rails" similar to AOL Server, and we did plenty of native bindings.