A number of current developments in the svn version:
- in-place recompilation: this allows you to update the code in all objects and their clones without needing a reboot. For those used to other lpc drivers, the 'deal' with this is that the objects in question are not replaced, hence all object references stay valid. Yet all objects and clones will get the new functionality inmediately.
- Support for using DGD as a persistent server. This requires the in-pace recompilation. What this means is that Gurbalib now handles using statedumps, and can properly restore and continue from one. Also, Gurbalib should not require reboots or such for updates or changes.
- Limited support for using Gurbalib to build a persistent world, cleanup and reset can be disabled and it is possible to drop an item somewhere, leave it alone for years, and then find it back when you return.
This weekend, we did some radical changes to the implementation of the this_player() and set_this_player() afuns. This makes them work as one would expect, but is having some repercusions. Mostly, there are a number of places in the lib that made some bad assumptions about what this_player() should be pointing to. Many of those have been fixed, but there are bound to be a few left still.
Also, somewhere this week most likely, a new security system will be committed to svn. Some details:
The new security system is capable of verification of all programs (not just objects) on the stack, and can be configured with 3 levels of security:
1. Only verify the rights of the current object
2. Only verify objects on the call stack (this mode is practically identical to the mudos/fluffos stack security implementation)
3. Verify both objects and inheritables on the call stack
As a consequence of this new security system, /obj/user.c, /obj/player.c, /std/user.c and /std/player.c will all be moved into /sys/
This allows for reducing the privileges of almost all code outside /sys and /kernel.
Other things expected in svn soon:
- new currency system
- new inventory handling
The repository is at svn://wotf.org/gurbalib
On behalf of the Gurbalib Resurrection Project,