Tcl - Re: Is there a dedicated TclDevKit forum?

Author

Re: Is there a dedicated TclDevKit forum?

mets

2007-06-07, 8:12 am

On 6 Jun, 18:55, Jeff Hobbs <j...@activestate.com> wrote:
> mets wrote:
>
> You are welcome to post them here, but unfortunately my usenet feed gets
> poorer by the year (many ISPs don't seem to value usenet anymore).
>
>
>
> You do not need to compile anything for starpacks. ActiveTcl includes
> basekits, and most other tclkits will work as well. As to question 1,
> what is really being asked? You can properly wrap itcl sources without
> problem, and they can also be bytecode precompiled by tclcompiler, but
> otherwise there is no need to "compile" itcl source, as itcl is a
> standard extension in ActiveTcl.
>
> Jeff

I see now that the 'wrapper' is not dependant on the 'compiler'ed tcl
source.
Maybe I need to read the docs more thouroughly, but I came across this
note and thought 'Hmmm'

>Tcl Dev Kit Compiler has these limitations:
>
>[incr Tcl] code is not compiled.
>Bodies of dynamically created procedures cannot be compiled.
>Procedures within the scope of namespace eval are not compiled

I really like the idea of keeping the source secure.

Jeff Hobbs

2007-06-08, 10:11 pm

mets wrote:
> I see now that the 'wrapper' is not dependant on the 'compiler'ed tcl
> source.
> Maybe I need to read the docs more thouroughly, but I came across this
> note and thought 'Hmmm'
>
>
> I really like the idea of keeping the source secure.

OK, that part is correct, although the wording can be confusing.
Switching between compiling, precompilation and bytecode obfuscation ...
while the itcl code does get compiled, it is not fully obfuscated, not
in the sense that each proc becomes a stream of indecipherable
bytecodes. This is done in part, but introspection will still reveal
public method bodies. Unfortunately the design of itcl does not make
this part easy to fix.

Jeff

Sponsored Links