A coupld ideas to throw around: >1. Multiple command interpreters. Instead of having a single interpreter, >do_interpret, use several, do_interpret_shop, do_interpret_olc (or >do_interpret_aedit, do_interpret_redit, etc.), do_interpret_combat where >each interpreter has its own set of commands (in a table/list) instead of >having one huge command table/list.
Well, OLC and the regular command commands are broken up. By dividing them, though, you would still need to scan them all or come up with a creative way to know which command was in which table. >2. Dynamically resolved command table/list - add a char* field (func_name?) >that is compared to nm output (unix/linux utility to list symbol names in >binaries/object files). I had this partially working awhile back, but lost >all progress dues to a freaky fs corruption :-( That's really cool, i've seen it.. But I'm not married enough to one OS to implement that. >3. As seen in my last email - A few methods for creating a *realistic* >dynamic map of game areas? I do that in my wilderness. But not areas. It's even exportable to jpg for web site viewing: http://www.pendulus.org/map/map.html >4. Pro/Con of changing all ROM singlely linked lists into doubly linked >lists? Can't think of any real cons, except for the time. It would be neat, but i've never found a real specific *need* for this. (Except for when you want something saved to a file the same way everytime) Not discrediting any ideas, just giving my opinions. Jason
