home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.tcl
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!rpi!sarah!cook!psinntp!psinntp!sugar!karl
- From: karl@NeoSoft.com (Karl Lehenbauer)
- Subject: Re: Tcl as a safe multimedia mail language (was Re: Insecurity of tk)
- Organization: NeoSoft Communications Services -- (713) 684-5900
- Date: Tue, 29 Dec 1992 15:15:24 GMT
- Message-ID: <C0111p.Ano@NeoSoft.com>
- References: <1992Dec28.004651.24596@walter.bellcore.com>
- Lines: 21
-
- In article <1992Dec28.004651.24596@walter.bellcore.com> Nathaniel Borenstein <nsb@thumper.bellcore.com> writes:
- >I wrote:
- >> You can test some of your ideas with respect to Tcl as a safe multimedia
- >> mail language without resorting to C at all -- if you use "rename" and
- >> rename a command to "", it is effectively deleted from the interpreter.
-
- >True, but dangerous. Before I would depend on this approach in a
- >production implementation, I would want to have a Tcl command that gave
- >me the names of all currently-defined Tcl commands. I could then use an
- >"OK" list instead of a "DANGEROUS" list, which sounds like a much safer
- >approach.
-
- Good idea. "info commands" will tell you the names of all currently
- defined commands (builtins and procs). "info procs" will give you the
- procedures but not the builtins.
-
- I agree security is critical, and problematic. Again, perhaps we could put
- multiple interpreters to good use here. K
- --
- -- Email info@NeoSoft.com for info on getting interactive Internet access.
- "In a minute, I'll burp up your droid."
-