muss Sun, Sep 16. 2007
muss is a concept for the sharing of common code between mu* servers.
Specifically, it will follow the musix standard. Only code following the standard will be put in
there.
Whether or not it will be a true library, or simply a source file, is unknown.
If a source file, all functions in it will be able to be disabled so that servers can continue to use their own if they
wish.
muss stands for MU* Shared Source, if it's not obvious.
musix Sun, Sep 16. 2007
musix is a proposal for a standard set of functions that exist on all MU* servers. There are many identical functions
that already exist, and more importantly there are plenty of nearly identical functions that could be made identical
with very little tweaking.
An example would be the htab interface. It predates the forking, and has remained basically unchanged. A few features
have been added to different implementations, but those can either trivially be added to others or left out of the musix
standard.
It's important to note that musix doesn't require any sharing of source, each function could be implemented separately
on different servers. Source sharing is in muss
No existing function names will be used. They will obviously be considered, but will be prefixed with a msx_
Over time, especially with muss, it's hoped that server code will be charged to call these standard functions instead of
their own. (Even if the standard function is just a macro to their own) in the hopes of writing code that can be shared
much more easily between servers.
The name 'musix' comes from 'posix' and stands for MU* System Interface.
Compatible string functions on PennMUSH and TinyMUX Tue, Aug 21. 2007
If you know what this is, you know what it is. If you do not, you do not.
Continue reading "Compatible string functions on PennMUSH and TinyMUX" »
« previous page
(Page 1 of 1, totaling 3 entries)
next page »