>I'm inclined to put access restrictions on "dangerous" commands in the >Interpreter. Pretty easy to do, actually. Such commands would include: > > set the script of > > open file > write to file > close file > >and quite a few more. > >I won't have code untrusted doing much more than addition on my machine :) Anthony, paranoia! I'm all for it. Cheers, -- M. Uli Kusterer ------------------------------------------------------------ http://www.weblayout.com/witness 'The Witnesses of TeachText are everywhere...'
- Re: OODL: Licence to use for code DeRobertis
- Re: OODL: Licence to use for code M. Uli Kusterer
- Re: OODL: Licence to use for code MP0werd
- Re: OODL: Licence to use for code M. Uli Kusterer
- Re: OODL: Licence to use for code DeRobertis
- Re: OODL: Licence to use for code M. Uli Kusterer
- Re: Re: OODL: Licence to use for code MP0werd
- Re: Re: OODL: Licence to use for code MP0werd
- Re: Re: OODL: Licence to use for code M. Uli Kusterer
- Re: Re: OODL: Licence to use for code DeRobertis
- Re: Re: Re: OODL: Licence to use for code M. Uli Kusterer
- Re: Re: Re: OODL: Licence to use for code MP0werd
- Re: Re: Re: OODL: Licence to use for code M. Uli Kusterer
- Re: Re: Re: OODL: Licence to use for code DeRobertis
- Re: Re: Re: OODL: Licence to use for code M. Uli Kusterer
- Re: OODL: Licence to use for code Mark Rauterkus