unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 25017@debbugs.gnu.org
Subject: bug#25017: Fwd: Re: dotimes var comiler warning
Date: Thu, 24 Nov 2016 17:50:37 +0100	[thread overview]
Message-ID: <87ziko4yaq.fsf@web.de> (raw)
In-Reply-To: <87zikpkkej.fsf@gmx.de> (Michael Albinus's message of "Thu, 24 Nov 2016 15:44:04 +0100")

Michael Albinus <michael.albinus@gmx.de> writes:

> > Yes, you can probably use `_' to suppress the warning, but I always
> > wondered why something called like this requires a variable to be
> > specified (mandatorily) at all.
>
> Why is this a problem? We have the same situation with function
> arguments. If you have an unused argument, you do the same:
>
> (defun my-fun (_unused used)
>   ;; code w/o _unused
>   )

It's not a problem.  But it's counter-intuitive for something called
"dotimes", and it's inconvenient because not needing to bind the counter
to a variable is a very common use case, not an exception.

But yes, it's just a detail.  If what I suggest is not consent, I would
not want endless debates on this topic.


Michael.





  reply	other threads:[~2016-11-24 16:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878ts957gj.fsf@web.de>
2016-11-24 14:10 ` bug#25017: Fwd: Re: dotimes var comiler warning Andreas Röhler
2016-11-24 14:23   ` npostavs
2016-11-24 14:35     ` Michael Heerdegen
2016-11-24 14:44   ` Michael Albinus
2016-11-24 16:50     ` Michael Heerdegen [this message]
2016-11-24 17:01       ` Michael Heerdegen
2016-11-25  6:03         ` Drew Adams
2016-11-27 10:20           ` Michael Heerdegen
2016-11-27 18:23             ` Drew Adams
2016-11-27 20:11               ` Philipp Stephani
2016-11-28 16:31                 ` Michael Heerdegen
2016-11-28 16:54                   ` Drew Adams

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=87ziko4yaq.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=25017@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).