[MUD-Dev] Object and class heirarchies -- are they really necessary?

[Par Winzell]

J C Lawrence writes:

 > FWIW: Larry McVoy (BK author) is keen to see BK used as an embedded
 > tool FWIW and has been conciously re-writing some of the APIs and
 > access points to make it easier to embed.  I could easily see having 
 > an external DB (ala MySQL, SOLID, (g/n/*)dbm, whatever) with the
 > edit interfaces running thru BK for all object code changes...

This is very exciting! I spent some time searching the net for library
implementions of RCS, but failed utterly. I was ready to call binaries
for the revision control aspects of the Skotos development system, due
for implementation in the weeks to come. I'll definitely take a closer
look at BitKeeper when they do their source release.

Revision control on a file by file basis is one thing, but yes, as you
point out, being able to do release-style state snapshots is where the
real benefits would lie -- at least for emergency recovery purposes...
It's possible to get a little carried away here, but there's no reason
not to start simple and grow more power in time.

Thanks!
Par




_______________________________________________
MUD-Dev mailing list
MUD-Dev at kanga.nu
http://www.kanga.nu/lists/listinfo/mud-dev