It does seem that way. I've rewritten most of the network code in LambdaMOO 1.8.1+foo, since it was, well, ancient and disgusting. (sorry, but there hasn't been a need to use /dev/tcp on Solaris in the last, oh, ten years :P)
Now the network stuff at least is sane. Too bad I've still gotta eventually rewrite the memory stuff / ref counting - it's horribly broken on Alpha, and very very poorly designed in the first place. (don't believe me? watch the infinite loop you get when trying to load a working core into a lambdamoo binary linked against electricfence..)
The lambda+foo project is basically aimed at (some day) having a good MOO server based on the old code but with all the glaring problems fixed. Some day might be quite a while away, but we have improved things a bit, at least.
So we have lambda+foo, GammaMOO, etc, ... it seems awful that we need all this forking.
Also, with 32-bit computers on the way out, dumping the use of symlinks for floating-point numbers is a good thing, and similarly, we should enable Unicode handling.
I guess what I'm asking is: is there any reason to not do this kind of work against the CVS tree on Sourceforge, and to pick someone as release coordinator, for something we can call 1.9.0 or 2.0.0?
-hpa
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
