falsissime

11 ms·

31.
by falsissime 7y ago
See https://github.com/mthom/scryer-prolog/issues/251
32.
by falsissime 7y ago
There are two different notions of type here. One is determined by the abstract syntax, in this context a variable is a type, that's what you are referring to. With this type no desirable algebraic properties hold like commutativity, s
33.
by falsissime 7y ago
(I do not agree, but let's rather take a sharper example) Consider atomic(T) and T =.. [_] or functor(T,_,0) which describe exactly the same except that atomic(T) similar to integer(T) silently fails and T =.. [_] and functor(T,_,0) pr
34.
by falsissime 7y ago
Out of curiosity: What did f 0 0 give for f _ 0 = 1; f 0 _ = 2; ?
35.
by falsissime 7y ago
Some of your points are taken seriously! Think of purifying Prolog such that cuts and the like are (for many cases) no longer needed, yet you get comparable efficiency. See library(reif), library(pio), ... Think about implication in proposi
36.
by falsissime 7y ago
There are already many built-ins that behave in exactly the same manner as integer_si/1 does. Take T =.. [F|Args]. which produces an instantiation error, idem functor(T,F,1). The nice thing when you have (such) errors is that if they d
37.
by falsissime 7y ago
Should have been EUR in place of $
38.
by falsissime 7y ago
Right, that would be a valid answer too! Unfortunately it has very bad termination properties and is also quite inefficient when larger numbers are involved. And yet, there is a further possibility why not say `when(nonvar(X), integer(X))`
39.
by falsissime 7y ago
$2250 is the first year. Then $750 a year. This includes support. To my understanding, development alone without distribution falls under the personal license.
40.
by falsissime 7y ago
https://sicstus.sics.se/order4.html Includes an evaluation license (free) and a personal license for EUR 165.
41.
by falsissime 7y ago
Do not forget SICStus, it´s jitter is truly excellent.
42.
by falsissime 7y ago
The most difficult to understand aspect of the WAM are its put_unsafe instructions which permits WAM's incredibly simple LCO. You can only appreciate its ingenuity after you had struggled with last call optimizations in engines like t