From: Jim Ottaway <j.ottaway@lse.ac.uk>
Subject: Re: puzzling byte-compile-file message: `=' called for effect
Date: Tue, 15 Nov 2005 17:12:46 +0000 [thread overview]
Message-ID: <87ek5hltrl.fsf@lse.ac.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 83 bytes --]
Sorry, I meant to cc this to the emacs-devel list, but forgot to add
the header.
[-- Attachment #2: Type: message/rfc822, Size: 1692 bytes --]
From: Jim Ottaway <j.ottaway@lse.ac.uk>
To: help-gnu-emacs@gnu.org
Cc:
Subject: Re: puzzling byte-compile-file message: `=' called for effect
Date: Tue, 15 Nov 2005 17:09:35 +0000
Message-ID: <87lkzpltww.fsf@lse.ac.uk>
>>>>> Drew Adams <drew.adams@oracle.com> writes:
> The term "for effect" is correct here, but I don't think it is as clear as
> it could be. The compiler is suggesting that, if the `=' expression is
> useful, it must be useful because of side effects that occur during its
> evaluation.
> I think the compiler should explicitly say that the resulting _value_ of the
> `=' expression is not used. It might also say that the `=' expression may be
> useful for its side effects (or side effects of its subexpressions), but the
> resulting value has no effect on the overall code. At a minimum, the word
> "side" should be added to "effect".
Yes, I agree. I was so puzzled by the elliptical message that I
missed the obvious error in my code.
> The message might better say:
> "Warning: `=' return value ignored. Is the expression useful
> for its side effects?"
Something like that, I agree, even simply "`=' called for side effect
alone".
> Ccing emacs-devel, as I think the message should be clarified
> somehow.
Me too.
Regards,
--
Jim Ottaway
[-- Attachment #3: Type: text/plain, Size: 18 bytes --]
--
Jim Ottaway
[-- Attachment #4: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2005-11-15 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 17:12 Jim Ottaway [this message]
[not found] <437A07CF.2030008@cs.indiana.edu>
2005-11-15 16:39 ` puzzling byte-compile-file message: `=' called for effect Drew Adams
2005-11-15 23:22 ` Richard M. Stallman
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=87ek5hltrl.fsf@lse.ac.uk \
--to=j.ottaway@lse.ac.uk \
/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).