Hi!
> Thomas wrote:
> > You have to differentiate between determinism "by contract"
> > (I assume Chris means this one) and "by implementation" (that's probably
> > what Lewis is talking about.)
> > That is, a system can be non-deterministic by contract (or conceptually)
> > while its actual behaviour, as implemented, can be "somehow
> deterministic." Be careful, though, to rely upon this "accidental"
> determinism, because the behavior might change if any modifications
> to the implementation are made.
> Ok so I've got this AI system which transports water molecules from A to
> B - a pipe. It uses IF, THEN rules. Can achong know where a specific
> molecule is at a specific time ? Complex system theory, quantum mechanics,
> Shroediger's cat - let's not get into religion !
This is not about religion but about correct software engineering and perhaps about
"the right tool for the right task" (as Ernest always says.) If you have a tool/system
that does not guarantee (i.e., offer a contract, cf. "design by contract") a certain
behavior (e.g., a deterministic evaluation order of rules having the same salience) or
quality of service, it's most probably not the right tool (or approach), if you need
to rely upon that behavior or quality of service.
> This mailing list is for jess USERS, not re-designers.
I'm not sure what you mean by "re-designers", but this list has seen discussions about
extensions, redesign/refactoring, and user contributions.
Thomas
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list (use your own address!) List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
