Parser

[gumby]

I've been toying with the idea of porting a new parser for SCI.  I know where to insert it into the current scripts, so that part is done & tested.

I've been looking at using the Inform parser which I've been working with quite a bit lately.  It is really robust, almost too robust.  I think there shouldn't be any problem with data types & storage,  I am concerned about the heap however.  I'm not sure what other limitations there might be here.  I believe I read somewhere that the longest input string in SCI could be 50 (or maybe I saw that in the code) which is probably OK.

Thoughts?

[Collector]

Could this be done without other changes to SCI? I suppose if any, it would be mostly with the template game. I'm just wondering about any kind of compatibility problems.

[gumby]

Could this be done without other changes to SCI? I suppose if any, it would be mostly with the template game. I'm just wondering about any kind of compatibility problems.

I think so.  All the logic would be performed in procedures & methods, just like all the programming for SCI games is done now.  So as long as the game can be compiled (and rendered bug-free) it should be fine from a compatibility standpoint.

[gumby]

After further investigation, I'm not sure this is worth the effort.  I guess lets just 'fix' the shortcomings of the existing parser with custom scripting.

[Collector]

Is there anything in the source of Studio that may help? Again it would be good if we had the source for Companion.

[MusicallyInspired]

The current parser is embedded in the interpreter. Adding a new parser via scripting would definitely introduce heap issues, I'd think. To replace it any other way would mean rewriting the interpreter itself, which is out of the scope of Studio/Companion.

[Cloudee1]

Are we using the best interpreter for the job?

[MusicallyInspired]

We're kind of limited to whatever version of the interpreter Brian turned into the template game.

[Collector]

IIRC, Brian used Larry 3 for the template game. Would Hero's Quest or QfG2 provide a more robust interpreter and what would be involved with creating another template game

[MusicallyInspired]

I honestly have no idea. If any of us did I image we'd have done something with the SCI Studio VGA source code by now.

[Collector]

If any of us did I image we'd have done something with the SCI Studio VGA source code by now.

True

[MusicallyInspired]

I'd personally like to have the KQ1SCI interpreter because it supports scrolling backgrounds.

[Collector]

So did SQ1SCI, but of course that was not SCI0.