Non-debug code should *never* use object numbers in the first place. The
closest thing should be properties on the object which contain the
object number.
What you are proposing would probably be more like this (though some
things, for example "$ldd" might end up being different, and as I don't
have the resolv API memorized, the verb names might be wrong too):
netapi = this.netapi = $ldd:load("resolv", "2.2.5");
netapi:connect("127.0.0.1", 8888);
Outside of the MOO environment, the language could be used to write
applications just like most that are currently written in C or C++. Many
people, myself included, don't like C++ and C&/MOOcode would be a nice
replacement.
The MOO server can continue to be updated to support changes we make,
but it is still a seperate project. It would mostly be a C&/MOOcode
interpretor with some MOO-specific assumptions such as the MOO network
API and various other things.
The main efforts of this project would be to extend and document the
C&/MOOcode language. Side goals would be a compiler and interpretor, the
latter likely being based on the LambdaMOO server.
On the subject of the LambdaMOO server, there is a WAIF fork of the
LambdaMOO server in the CVS. Unicode, I have yet to see, but I expect
that UTF-8 will likely be accepted as the format for C&/MOOcode strings
in the future. I never heard anything about SSL for MOO, but I would
like to know if someone's done stuff in this area... File access appears
to still be patches-only last time I checked.
ben and bjj are still working on the LambdaMOO server and the CVS is,
I've found, quite stable. There aren't really enough changes in it to
warrant a 1.8.2 release yet (or so I believe is the reason). Perhaps
they want to merge WAIFs into the main tree before releasing it, I'm not
sure.
Robert Sanderson wrote:
>Object refs will be meaningless outside of a MOO server. Already there's
>enough trouble with using them in code in a database portable fashion, and
>hence the proliferation of $foo.
>
>#1444:run_network_command("connect") is meaningless outside of an
>environment in which #1444 exists and has a callable verb called
>'run_network_command'.
>
>What possible use would the MOO language be outside of a MOO server?
>
>I'm all for advancing the language, but there are enough high level
>languages out there. We don't need another one, as much as I like MOO.
>Effort should go towards updating the server we have, for example
>inclusion of Lao Tzu's unicode patch, among others, and a distribution of
>1.8.2.
>
>Rob
>
>
>
Quinn wrote:
>
>It really doesn't matter, unless he would have putting his efforts
>towards an official new server release.
>
>Why haven't we had a new server release? Aren't there many patches
>worthy of being included? What about WAIFs? Unicode? Did SSL fall
>by the wayside? Fileutils?
>
>Is there anyone out there who has the skill, time, and desire to
>actually produce new LambdaMOO server releases?
>
>-Quinn
>
>
#############################################################
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]>
