Bugs for Sorcery are reported here

[bugzilla-daemon AT metalab.unc.edu]

http://bugs.sourcemage.org/show_bug.cgi?id=4003

acedit AT armory.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|sm-sorcery-                 |acedit AT armory.com
                   |bugs AT lists.ibiblio.org      |



------- Additional Comments From acedit AT armory.com  2004-06-05 18:37 -------
In my never ending quest to comment on all the sorcery bugs...

Im sure everyone has realized this, but just so this is documented,
the problem with making a grimoire a spell is that you wont get the new
providers/spells until after the grimoire is added, and if they have
depends of their own, they can't be dealt with until the grimoire is
added, which wouldn't happen until its too late.

Depending on another spell implies that you resolve that spells dependencies 
/before/ you ask the user "Do you want to cast these". Without the spell
actually being there we can't do that. The only other solution is to
break that guarantee and either not resolve depends (which would probably
make the spell fail), or we could ask questions again in the middle of all
the casting. To me thats a giant step backwards, and Im not coding it :)

So instead we go with the grimoire_[optional_]depends keyword. Except at
that point we have to get the grimoire before casting begins.

The "right" way to do this is to queue up all the grimoire requests
and continue resolving dependencies until you can't go on, then add
the grimoires, then resolve the spells in the new grimoire (and repeat
as necessary). The "easy" way to do it is when one comes across a
grimoire depends, we  download the grimoire right then and there
and too bad if you're on dialup and have to wait for a while, and then
have cast come back and start asking questions again.





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.