On #include:
>> >Scott Raney and I have discussed include several times, but
>> >besides being unable to come up with a comprehensible name ("include"
>> >really says nothing, does it?),
>>
>> I don't see why not. It's an imperitive... It tells the compiler: "Include
>> whatever [into my source]"
>
>But *when*? When the application starts up? When the stack opens?
>When that object opens? When it gets its first message? What happens
>when the user edits the script with the #include? Or edits the file
>(or the script of the other object) that gets included?
One way to reap the benefits of #include within the framework of the
existing xTalk world has been doable in a slightly different manner,
thanks to MC's editScript message:
You can have #include'd code inserted into the actual script when the
script editor closes, with only some minor modifications to the existing
editor.
But in practice, I've found the flexibility of "insert" and "start using"
have pretty much obviated this need for my own work.
- Richard Gaskin
Fourth World
Tools and services for multimedia and internet developers
__________________________________________________________
[EMAIL PROTECTED] http://www.FourthWorld.com
US: 800-288-5825 Int'l: 323-225-3717 Fax: 323-225-0716
