Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 7556] Cast doesn't terminate when casting spells that no longer physicaly exist

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT metalab.unc.edu
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 7556] Cast doesn't terminate when casting spells that no longer physicaly exist
  • Date: Fri, 22 Oct 2004 08:05:14 -0400

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





------- Additional Comments From BearPerson AT gmx.net 2004-10-22 08:05 -------
Really. Should we add a warning "if you change this, you have voided your
warranty"?
I mean, this sounds like "I killed 10 processes that were taking up too much
mem. My computer stopped working. Where can I file a bug?"
The index file is never wrong. Period. There is no way the grimoire can get
changed by sorcery without a reindex.

My point is: If you do things you're not really supposed to without fully
understanding/doing what you're supposed to do, things will break. That is the
reason why a warranty expires when you start fiddling with stuff.

After any changes to the grimoire, scribe reindex HAS TO be run. As andrew
stated nicely, the purpose of a cache is to be as up to date as the thing it's
caching. It's the same here.

Of /course/ we could add >1024 sanity checks to sorcery - md5sum checks of the
sorcery scripts... Checking every single environment variable... cleanse --fix
all of the basesystem before every cast... There are perfectly good reasons to
do all those, but also >10 good reasons not to.



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




Archive powered by MHonArc 2.6.24.

Top of Page