> >I agree. We're really talking about a load of bullshit that's unimportant
> >@ this stage. How about a "file view" of all the files included. We can
> >drag-drop and import. Wouldn't that suit the purpose much better?
>
> Dylan,
>
> I personally also consider include to be something that's not very useful
> in OpenCard. But if you consider we have a stand-alone interpreter planned
> as one of the milestones before we get to the actual OpenCard application,
> this interpreter might have a use for "include" and as it'll only execute
> one text file and then quit, there's no problem with adding a "include"
> feature there. But it should be a simple preprocessor token that's replaced
> with the file it includes. For that Anthony has my "go ahead" if he
> encloses it in a compiler flag so we can leave it out of OpenCard.
No no no no no no. Lets just have project files, or makefiles that you can put
whatever source files you want to include into. It is simply then a matter of
compiling all the text from the files as one script. Include is so
unnecessary. You could have a start using for precompiled libraries though. I
would be cool with that.
Andre
