![]() |
|
|||||||
| Notices |
![]() |
|
|
Thread Tools | Display Modes |
|
|
#1 |
|
Guest
Posts: n/a
|
"find": AND/OR no longer equal precedence
There was a time when I used HP-UX and Solaris, and the "find"
command's AND (implied) and OR operators were of equal precedence. Basically, operators were evaluated from left to right. I am currently using GNU "find" version 4.3.8, and the AND operator has greater precedence than the OR operator. When did this unequal precedence start to become standard (assuming that it is standard) It certainly is more intuitive, though we have to be careful of falling back on old ways, and maybe need to rework old scripts? Is it pretty well the way that *nix is going? Thanks. Fred |
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|
< Windows Help - MS Office Help - Hardware Support >
| New To Site? | Need Help? |