Public SourceMage Discussion List

[Ryan Abrams <rabrams AT sourcemage.org>]

My first guess on how to do it would be this:

Reduce Sorcery to a DETAILS and a DEPENDS.

Have a catch in sorcery that says "if sorcery is in the queue or being 
cast, immediately stop the casting of the queue, and run 
sorcery_update.sh"

Then we write a nice sorcery_update.sh that does the work, and make 
sure that when it ends, it drops people back into whatever they were 
doing. (probably possible via an env variable or something)

Anyway, thats a first bash at it... what ideas do you have?

-Ryan

On Thursday, September 12, 2002, at 08:19  PM, Nick Jennings wrote:

> On Thu, Sep 12, 2002 at 04:22:43PM -0500, Ryan Abrams wrote:
> > Hmm.. could we take a dual approach? a "sorcery" spell which does 
> > nothing
> > but list depends and stay sustained, and an "update_sorcery" function 
> > in
> > sorcery itself? As far as gaze version and such, you are write. But 
> > users
> > could jsut run sorcery and look. Not /as/ nice, but its there.
>
>  Well, possibly. However the more I think about it, the more I agree
>  that sorcery probably would do best *not* being a spell. However
>  we really need to think about how things should behave in this
>  respect.
>
> > I dont know. It just seems like using sorcery routines to update 
> > sorcery
> > routines is inherently unstable, because at some point in the 
> > process, the
> > system is hosed on the disk, and sorcery only exists in memory. and 
> > that
> > leads to crap like power outages hosing systems... or 1 bug in a spell
> > leaving a system hosed.. etc.
>
>  I agree completely.
>
> - Nick
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss