| 1 |
On Wednesday, October 13, 2010 15:37:02 Ulrich Mueller wrote: |
| 2 |
> >>>>> On Wed, 13 Oct 2010, Mike Frysinger wrote: |
| 3 |
> > # If no paths are specified, then the return value is "false". |
| 4 |
> |
| 5 |
> For the "or" case that's fine. But for the "and" case, I would expect |
| 6 |
> that the function returns true if called with no arguments. |
| 7 |
|
| 8 |
i disagree as the comment says: it's sticking to the bash behavior. |
| 9 |
|
| 10 |
f= |
| 11 |
[[ -e ${f} ]] && [[ -e ${f} ]] |
| 12 |
[[ -e ${f} ]] || [[ -e ${f} ]] |
| 13 |
|
| 14 |
these both return false. as does this function: |
| 15 |
|
| 16 |
f= |
| 17 |
path_exists -a ${f} |
| 18 |
path_exists -o ${f} |
| 19 |
-mike |
Archives