This is the mail archive of the
xconq7@sources.redhat.com
mailing list for the Xconq project.
Re: time.g weirdness
> (set relative-infinity 9999)
Is this better than adding infinity to the lisp object system (with
infinity getting its own value in enum lisptype)? I guess for the
latter you'd need to figure out comparisons, arithmetic, etc, anew,
which might be a bit of a pain. And of course there would be the
problem of when it is brought into C code, does it turn into TABHI, or
does the code need to check for it specifically, or what?
What I had in mind was something much less deep. If
mp-to-enter-terrain says you need 99 movement points, and
acp-per-turn, free-mp, etc, say that a unit can never get 99 movement
points in a turn, then have the help report it as infinite. The big
problem with that is that it is very case-by-case, and it would be
easy for this computation to be out of sync with the action code. So
maybe one of the infinity variants would make more sense anyway.