unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@online.de>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Alan Mackenzie <acm@muc.de>, 33314@debbugs.gnu.org
Subject: bug#33314: 27.0.50; wrong compiler warning
Date: Fri, 9 Nov 2018 09:35:04 +0100	[thread overview]
Message-ID: <42275e81-12d5-e38b-86f2-7c9ba2c62cfe@online.de> (raw)
In-Reply-To: <87wopngimi.fsf@gmail.com>



On 09.11.2018 02:11, Noam Postavsky wrote:
> tags 33314 unreproducible moreinfo
> quit
> 
> Andreas Röhler <andreas.roehler@online.de> writes:
> 
>> So regexpvalue is used too. May send the complete function if interested.
> 
> Please do, I can't reproduce the warning you claimed in your original
> report (and frankly, I think you've been doing this long enough that you
> should know by now that such an abbreviated report is not very helpful).
> 
> Trying to fill in your example like this:
> 
>      ;;; -*- lexical-binding: t -*-
> 
>      (defun foo (regexp &optional something)
>         "..."
>         (unless (bobp)
>           (when (empty-line-p) (skip-chars-backward " \t\r\n\f"))
>           (let* ((orig (point))
>                  (regexpvalue (if (eq regexp 'py-clause-re)
>                                   (symbol-value
>                                    'py-extended-block-or-clause-re)
>                                 (symbol-value regexp))))
>             t)))
> 
> gives
> 
>      bug-33314-bcomp-warning.el:3:1:Warning: Unused lexical variable ‘regexpvalue’
>      bug-33314-bcomp-warning.el:3:1:Warning: Unused lexical variable ‘orig’
>      bug-33314-bcomp-warning.el:3:1:Warning: Unused lexical argument ‘something’
> 
>      In end of data:
>      bug-33314-bcomp-warning.el:13:1:Warning: the function ‘empty-line-p’ is not
>          known to be defined.
> 
> `regexp' is not mentioned, but the other unused variables are, as
> expected.
> 

Hmm, sorry, can't reproduce it any more. As this happens from time to 
time, should send a complete report indeed. Tried to replay for now, but 
couldn't find a saved state.

Thanks for your care,

Andreas





      reply	other threads:[~2018-11-09  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 14:38 bug#33314: 27.0.50; wrong compiler warning Andreas Röhler
     [not found] ` <mailman.3649.1541688141.1284.bug-gnu-emacs@gnu.org>
2018-11-08 15:54   ` Alan Mackenzie
2018-11-08 16:41     ` Andreas Röhler
2018-11-09  1:11       ` Noam Postavsky
2018-11-09  8:35         ` Andreas Röhler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42275e81-12d5-e38b-86f2-7c9ba2c62cfe@online.de \
    --to=andreas.roehler@online.de \
    --cc=33314@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=npostavs@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).