At 7:25 AM +0100 on 11/25/99, M. Uli Kusterer wrote:
>>True. I think we should ditch the built-in dial command, add full control
>>of serial ports, and then just have a dial function in the home stack.
>
>Anthony,
>
> Would work if we allow multiple stacks in one file. Then we could just
>merge a home stack with minimal contents into the standalone. If we gave
>the users a choice which home stack to include, they could create their
>custom versions that don't have certain commands, or could add commands
>like dial etc. they need and start using that stack.
Multiple stacks in a single file... hmmm... sounds like a XBF issue. The is
no reason why it would be hard to implement, except in XBF.
If you do decide to implement it in XBF, I'd suggest allowing the blocks
from different stacks to be intermixed -- otherwise you're dealing with
moving whole stacks around. Perhaps you could have additional subblocks:
Make all the items in a stack sub-blocks of one stack object.
> I don't think we should allow any syntax structure to be plugged in,
Thankyou... I'm QUITE glad about this :)
>but
>adding support for additional commands and functions won't be that hard, I
>guess. You'd just have to look up every command in a list to which plug-ins
>would be added, too.
It won't require much extra code. Interpreter already has plugin functions
-- though they're presently written in NuTalk. It also has ones written in
C. No problem having ones put in a shlb. [This refers to the present
interpreter, not the new one which I've got to write].
