[m-rev.] diff negation in trace goals conditions

Ondrej Bojar bojar at csse.unimelb.edu.au
Thu Feb 22 07:19:03 AEDT 2007


Yes, boolean expressions can be negated. Maybe the wording is not quite clear? 
Or maybe it is not clear given my previous proposal but it would be clear alone?

Part of the diff I already posted:

Index: doc/reference_manual.texi
===================================================================
RCS file: /home/mercury/mercury1/repository/mercury/doc/reference_manual.texi,v
retrieving revision 1.383
diff -u -r1.383 reference_manual.texi
--- doc/reference_manual.texi   13 Feb 2007 12:35:04 -0000      1.383
+++ doc/reference_manual.texi   21 Feb 2007 11:02:16 -0000
@@ -9340,8 +9340,8 @@
  or it has to be compiled in a debugging grade.

  In general, the single argument of the @samp{compile_time} function symbol
-is a boolean expression that may use the @samp{and} and @samp{or} operators
-to connect one or more primitive compile-time conditions.
+is a boolean expression that may use the @samp{and}, @samp{or} and @samp{not}
+operators to connect one or more primitive compile-time conditions.
  There are three kinds of conditions.
  The first has the form @samp{flag(@var{FlagName})},
  where @var{FlagName} is an arbitrary name picked by the programmer;
@@ -9362,8 +9362,8 @@
  (It doesn't matter what value it is set to.)

  In general, the single argument of the @samp{run_time} function symbol
-is a boolean expression that may use the @samp{and} and @samp{or} operators
-to connect one or more primitive compile-time conditions.
+is a boolean expression that may use the @samp{and}, @samp{or} and @samp{not}
+operators to connect one or more primitive run-time conditions.
  There is just one condition.
  It has the form @samp{env(@var{EnvVarName})},
  this condition is true


O.


Julien Fischer wrote:
> 
> On Wed, 21 Feb 2007, Ondrej Bojar wrote:
> 
>> Incorporated Zoltan's and Julien's comments, will commit tomorrow 
>> unless more comments appear.
>>
>> Estimated hours taken: 2
>>
>> Added support for negation in conditions (run_time and compile_time) 
>> for trace
>> goals.
> 
> 
> Can you now negate non-primitive conditions?  The test case you posted
> suggests so, but the reference manual still restricts negation to 
> primitive conditions.
> 
> Julien.
> --------------------------------------------------------------------------
> mercury-reviews mailing list
> Post messages to:       mercury-reviews at csse.unimelb.edu.au
> Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
> Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
> --------------------------------------------------------------------------
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------



More information about the reviews mailing list