------- Comment #2 from ronald dot pucul at l-3com dot com 2007-12-13 23:28 ------- Subject: RE: gnatprep evaluating "not" operator at incorrect precidence
Sorry, I had assumed gnatprep would follow the same rules of precidence as the ADA RM requires. I had not known this not mixing of "not" and "and" or "or" rule was established.(operation changed someplace between 3.3.3 and 3.4.1) On the version included with gcc-3.3.3 the gnatprep tool performs the evaluation for "not" operator / keyword acording to the ADA RM precidence. The GNAT RM on gcc.gnu.org doesn't precicely indicate one way or other how/when "not" should be evaluated. I'll "patch" the gcc-3.4.6 version of gnatprep for our internal use until the 2000+ lines(approx 400 source files) not currently following the NEW rule are modified. Thank You for the info. Ron Pucul -- Old/tired sftwr. eng. here @ L3 Link. > -----Original Message----- > From: sam at gcc dot gnu dot org [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 13, 2007 7:40 AM > To: Pucul, Ronald E. @ Link > Subject: [Bug ada/34446] gnatprep evaluating "not" operator > at incorrect precidence > > > > ------- Comment #1 from sam at gcc dot gnu dot org > 2007-12-13 13:39 ------- This is fixed in SVN trunk: > > ==============Error messages for input file: thing.in > 1. # if not VAR_TRUE or VAR_TRUE then > | > >>> mixing "not" and "or" is not allowed, parentheses > are required > > 5 lines: 1 error > > > -- > > sam at gcc dot gnu dot org changed: > > What |Removed |Added > -------------------------------------------------------------- > -------------- > Status|UNCONFIRMED |RESOLVED > Resolution| |FIXED > Target Milestone|--- |4.3.0 > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34446 > > ------- You are receiving this mail because: ------- You are > on the CC list for the bug, or are watching someone who is. > You reported the bug, or are watching the reporter. > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34446
