On Sat, 25 Jan 1997, Justin Rio wrote: > If anyone is kind enuf and feels like they have the time, you know what > would help me out? A flowchart diagram, showing which file circle code > goes to for what. Okay, comm.c handles the communication btwn player and > mud, right? Okay, let's say I send the command "cast 'magic missile' > fido", what's it do from there? "cast" would be the first step; is that > done inside of comm.c? When it knows "cast" is the command, where does it > send the command next? > Am I making any sense? Okay, here's a rough outline of where the input would go. This skips the queueing, main loop, etc. which would be called, and remains fairly high level (for the sake of breverity). The input would be received in one of "comm.s"'s functions and be passed on to the the intepreter (in interpreter.c). The interpreter would determine which function to call (in the cast of "cast", it'd be do_cast) and would call the function. -receives "cast" -command_interpreter calls do_cast -do_cast parses arguments and does the casting Simple, enough, I think. The same goes for other commands. When you are logging into the MUD, your input is sent to nanny(), which is the connection handler, instead of the command parser. -- Daniel Koepke dkoepke@california.com Forgive me father, for I am sin. +-----------------------------------------------------------+ | Ensure that you have read the CircleMUD Mailing List FAQ: | | http://cspo.queensu.ca/~fletcher/Circle/list_faq.html | +-----------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/18/00 PST