Bobby Hicks wrote:
Actually, I was thinkin more along the lines of having the mud sort of
"compile" the code on the fly. Maybe make the module kind of like
mobprogs are done. But, would be more readable and easier to use. Well,
sort of. More like C code but in a separate file and the mud would read
it, compile it, and load the module.
Since I'm coding my mud up in linux, I don't think the dll option would
be my best bet. Esp since I don't know how to create dll's for linux.
;p
Maybe you should look at integration of Cint
(http://root.cern.ch/root/Cint.html) into your project.
Or maybe you would like SWIG (http://www.swig.org)
Passing data in/out of these things becomes an issue. One solution
would be entirely compile your mud in the (SWIG|Cint) interpreter and
then having a minimal wrapper which executes this dynamic code.
If you don't expose enough functions you start to miss the functions
that you didn't expose.
Or maybe you could really expand the mobprog system you have and use that.
