Hi again, I was looking at the SCVM code and noticed that it seems to use a sub-op table for certain opcodes (e.g. arrayOps, verbOps). This is different to SCUMMVM, which instead uses a switch in the opcode to determine the intended sub-op.
Looking at the sub-op table, it seems like a good idea. All of the sub-op's appear unique, and it pretty much cuts out using the switch statement. However there is the potential that someone could call an invalid sub-op like <roomOps><set actor costume>, which would actually work in SCVM, but fail in SCUMMVM and perhaps the LEC interpreters as well (although i have not attempted this so i don't know for sure). Which leads me to my question. Is there any reason (apart from what i have already mentioned) why the sub-op table is used in SCVM? Regards, James S Urquhart _______________________________________________ ScummC-general mailing list [email protected] https://mail.gna.org/listinfo/scummc-general
