1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
These are easy things I recommend to anyone interested in getting
their feet wet:
* Add verblist, codelist commands.
* Make it work with -w with no warnings.
* Expand on the help texts. Add anything that seems useful -
examples, longer descriptions, etc.
* Implement wizard commands to re-bless objects - make a user into a builder,
a programmer, etc.
* Implement a system parameters object. This would get system tuning params
set on it, like whether md5 crypting is on.
* Lambdamoo style genders, pronouns, and pronoun substitution code.
* Allow leaving off the close quote in user input, and still parsing it
properly.
* implement "get all from <foo>"
* Make GuestAllocators keep a log of the last n guests, when logged in and
where from, and give them a guestlog verb to pretty-print it.
These are harder things:
* make "all" work differently - for each available object, make it call
the verb on that object, first printing the object's name. That way
"look all" will work, etc.
* Make an automated system to make sure all moo features work.
* Benchmarks and optimizations.
* Consider overriding the equality operator on objects, so an Error will be
false. Ie, if you do
if ($ret)
It'd be nice if that if statement wasn't entered if $ret was an Error.
* multiple processes (threads) - just waiting on debian's perl package for
this one.
* quotas
* in chroot, gethostbyaddr fails. Fork a process before that to just do
hostname lookups (ugh).
* Change how "in foo" is parsed, so I can do "look ball in box in basket in
fred"
|
