> Probably won't need to be that big.. but I can see where it's less work.
Hey, less work is good work. ;)
> > else{
> > printf("Invalid Command '%s'.\n\r", *cmd);
> > return;
> > }
I had switched them around, assuming the likelihood of someone typing a valid
command to be higher than that of not. I forgot to remove the return...
thanks. (whoops)
> cmd is never freed in the case that the command isn't found in the table.
> My interpreter uses a hash table. I'm not sure that it actually speeds
> things up, I just have a thing for hash tables. About to put my
> skill/spell table in one as soon as I find an exceptionally round tuit.
It'll probably speed it up, it's just that mine works REALLY fast... and I
don't really know a better way. Hash tables would work just fine... I
suppose. It wouldn't even be that hard to implement. I suppose a hash table
would help if you had thousands of commands... ;)
Actually, though, what I was hoping to find out is if anyone thought the
CONCEPT for what makes the interpreter work is a good idea. Or do you folks
think it's a better idea to do it the way ROM does. (Remember: mine works
like null terminated command line arguments).
I was interested in ... feedback. I appreciate those of you who HAVE given
some feedback... (And ESPECIALLY Palrich for pointing out my idiocy! ;)
Hmmm... next on my agenda... ummm... anyone got an idea of what's VERY
central to ROM that might need some spiffying up? (Maybe nanny!!) Hmmm....
Input?
Or is this a dying list? *mutter*
Mark
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
