From jcrippen at gmail.com Sat Sep 11 22:10:26 2004 From: jcrippen at gmail.com (James Crippen) Date: Sat, 11 Sep 2004 14:10:26 -0800 Subject: [lmud-devel] Initial Test Spam Message-ID: This is an initial test spam message to stub the mailing list archives. LMud and CL-TELNETD are now hosted on Common-Lisp.Net! Huzzah! That means that real people can actually participate, if they can be bothered to waste time on such unimportant projects. I welcome all contributions. This semester at school I'm inundated by 18 credits worth of classes, so I won't have much time to hack, but I hope to at least give some thought towards what CL-TELNETD needs for it to become operational (thread safety, for one), and how LMud is going to glue CL-TELNETD into place within its driver. Please feel free to yabber about anything even remotely close to the topic. These lists should be pretty low traffic, so it's not as though the S/N ratio could get very bad. Cheers, 'james From lists at alphageeksinc.com Fri Sep 24 20:01:54 2004 From: lists at alphageeksinc.com (Heow Eide-Goodman) Date: Fri, 24 Sep 2004 20:01:54 -0000 Subject: [lmud-devel] re-inventing past mistakes Message-ID: <1096055861.932.18.camel@sushi> Guys, I've always been interested in writing a MUD in Lisp as I feel it is a very, very good implementation language. Especially since the programming aspect of most MUDs are often an afterthought. Anyway, I thought you'd be interested in this paper on the exact subject: http://web.archive.org/web/20031227104716/http://www.ccs.neu.edu/home/dougo/thesis/000824/proposal/ Also, an interestingly fresh approach is this approach: http://mooix.net/ Which although is implemented in Perl, attempts to create a cross-language platform so that objects can be implemented in something like say Scheme. I'm off to check out the CVS snapshot! Love MUDs, love Lisp, - Heow -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part URL: