[sr #104971] Feature request: ?: expression

Follow-up Comment #1, sr #104971 (project findutils): Interesting idea; please bring it up for discussion on the mailing list. ___ Reply to this item at: __

[bug #15195] misleading error message

Follow-up Comment #4, bug #15195 (project findutils): I've now fixed these too, I think. ___ Reply to this item at: ___ Message

[bug #15235] Leading directories are misparsed as expressions

Follow-up Comment #7, bug #15235 (project findutils): I've fixed the additional problems and applied the documentation parts of your patch. I edited the ChangeLog entry slightly before prepending it. ___ Reply to this item at:

[bug #15235] Leading directories are misparsed as expressions

Follow-up Comment #6, bug #15235 (project findutils): Also, your patch did not update find.1 or find.texi, so at least part of my patch is still valid. ___ Reply to this item at:

[sr #104971] Feature request: ?: expression

URL: Summary: Feature request: ?: expression Project: findutils Submitted by: ericb Submitted on: Tue 12/20/05 at 07:01 Category: None Prio

[bug #15195] misleading error message

Follow-up Comment #3, bug #15195 (project findutils): I agree you have fixed the empty parenthesis. But 4.3.1-CVS still has a buggy error message when ! is not followed by an expression: $ find ! find: invalid expression; you have too many ')' _

[bug #15235] Leading directories are misparsed as expressions

Follow-up Comment #5, bug #15235 (project findutils): Your patch is not quite right: +boolean +looks_like_expression(const char *arg) +{ + switch (arg[0]) +{ +case '-': + if (arg[1]) /* "-foo" is an expression. */ + return true; + else + return false