Hi.
I was just meditating about the possibility of making an ASCII
playerfile/objfile etc. The subjects concerning space, compatability over
systems and all that I am aware of. This is a question about how to
physically implement it in a stable fashion :)
I'll outline my ideas of how to do some of it, and then you're welcome to
add to it, etc :)
I dislike the idea of handling a BIG ascii playerfile like the binaty now,
just converted to ascii, as it's a big pile to search thru when
considering that my current binary players pfile is 4.5megs. So I thought
of making a 'index' of names file, and seperate player stat files, like
the plrobjs ones, would this be a good approach ? anyone got any pros and
cons compared to a BIG players pfile in ascii ??
thats it :)
Short is beautifull, ofcourse all the oher binary files should be
converted to ascii, but they're allready in a 'single player' format (i.e.
the plrobjs files), so it's 'just' making a bin -> ascii conversion uti
there and change the load/save routines for objs..
Anyone knows if there is anny efficience drawback on making the load/save
routines for an ascii file storing system, instead of the current binary
one ?
Regards,
Con.
d.
--
Rasmus Rønlev DOEK'94 WWW: http://www.econ.cbs.dk/people/raro94ab
Student instructor MUD: exiled.mud.circlemud.org 5000
199.199.16.100 5000
Student, B.Sc in Computer Science and Business Administration.
+-----------------------------------------------------------+
| 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/07/00 PST