> thanks for your answer. So you avoid inconsistent use of equality for
> records with ghost fields by preventing its usage in regular code. (I
> have still to understand the meaning of the ‘pure’ attribute).
Basically, the "pure" construct lifts a logic term (or predicate) to the
program
On Mon, 18 Feb 2019, Jean-Jacques Levy wrote:
> Dear Jean-Christophe and Friends,
> thanks for your answer. So you avoid inconsistent use of equality for records
> with ghost fields by preventing its usage in regular code. (I have still to
> understand the meaning of the ‘pure’ attribute).
Dear Jean-Christophe and Friends,
thanks for your answer. So you avoid inconsistent use of equality for records
with ghost fields by preventing its usage in regular code. (I have still to
understand the meaning of the ‘pure’ attribute). But in my case, ‘set_1000' was
used in regular code, with
