3 ms·
Here you go: vTcl -- just like Visual Basic 3.0. Also, you get to use Tcl instead of Visual Basic, so even better ! http://vtcl.sourceforge.net/ http://vtcl.
by rkeene2 8y ago
Here you go: vTcl -- just like Visual Basic 3.0.
Also, you get to use Tcl instead of Visual Basic, so even better !
http://vtcl.sourceforge.net/ http://vtcl.sourceforge.net/
- pjmlp 8y agoVisual Basic 6 compiled to actual native code though, while TCL teached me to never use such languages beyond bare scripting tasks. Even Visual Basic 3's P-Code interpreter was faster than TCL string based one.
- meredydd 8y agoWhat was the last version of TCL you used? These days they have an extremely cunning system involving multiple representations: Being TCL, every value is of course canonically a string, but if you do (eg) integer operations the result will be stored only as an integer until its needed as anything else. And the body of a 'proc' will be compiled to bytecode on first use, so subsequent calls will go much faster. One could even add a specialising JIT to this if you wanted to.
- pjmlp 8y agoVersion 8.x, the ones where bytecodes where introduced (1999 - 2003). Thing is, if you want to speak about modern TCL implementations, then the comparison needs to be against VB.NET, with its 64 bit SIMD aware JIT/AOT compilers.
- rkeene2 8y agoAlso, modern Tcl can be compiled to machine code to a large degree thanks to TclQuadCode and LLVM.