Re: Nonsensical byte compiler warning.

[Markus Triska]

David Kastrup <address@hidden> writes:

> So you are of the opinion that a function that calls any other
> function from more than one place is a grave problem, and the byte
> compiler is not supposed to be helpful with grave problems?

No, I think it's already good enough in this case. For example, set
`byte-optimize-log' to t. The warning is then preceded by:

  (char-before) ==>     (char-after (1- (point)))
  (if (and (= arg 0) (c-syntactic-skip-backward "^}") (eq (char-after
  ...) 125)) nil) ==> (progn (and (= arg 0) (c-syntactic-skip-backward
  "^}") (eq (char-after ...) 125)) nil)
  eq called for effect; deleted

I hope you find that remotely helpful.