Age | Commit message (Collapse) | Author | Files | Lines |
|
child being added or removed is false.
This is necessary, since (eg) adding a "false" value to an "and" can
change the value of the "and".
|
|
expressions that are always "true".
I considered trying to optimize by stripping NULLs out of "and" and
"or" expressions, but that seems a bit tricky. It might be more
straightforward if I introduce "true" and "false" expressions
explicitly, though (part of the trouble is that it's probably bad if
creation routines return NULL, and they can't currently return false).
|
|
The code was assuming that all the subexpressions started out "true",
instead of actually examining their values. That made it look like
every choice was deferred --> no solutions. There are still no
solutions, but hopefully the reason is different.
|
|
|
|
Current values aren't dumped at the moment.
|
|
resolver.
I don't normally commit broken code, but this is a huge rewrite, and
I'd hate to lose it if my hard drive blew up.
|