all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Drew Adams <drew.adams@oracle.com>,
	 help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Check for redundancy
Date: Wed, 24 Jun 2015 16:55:15 +0200	[thread overview]
Message-ID: <558AC4D3.6030509@easy-emacs.de> (raw)
In-Reply-To: <24a1b328-82a8-44ff-8f8d-1425ab89ab67@default>


Am 24.06.2015 um 15:23 schrieb Drew Adams:
>> is there a check for redundancy in code?
>> Byte-compile warnings seem not to cover this.
> I don't have an answer.  But maybe start by defining "redundancy".
> Do you mean more than one definition of something in a file?
> A function? variable? macro?

The term is not specific to programming: expressing things which have 
been expressed already.
Human language needs it, as we may not grasp the meaning at first time, 
also repeating contributs to sense sometimes.

WRT to programming: for example two or more  functions taking the same 
kind of arguments, producing the same result but are named differently 
and reside at different places in code.

Given these code is designed to be processed at same time and location, 
that would be redundant.

Pertains to all kind of definitions.



  reply	other threads:[~2015-06-24 14:55 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  9:29 Check for redundancy Andreas Röhler
2015-06-24 13:23 ` Drew Adams
2015-06-24 14:55   ` Andreas Röhler [this message]
     [not found]   ` <mailman.5580.1435157733.904.help-gnu-emacs@gnu.org>
2015-06-24 18:21     ` Stefan Monnier
2015-06-24 21:10       ` tomas
2015-06-25  3:23         ` Stefan Monnier
2015-06-25  7:47           ` tomas
2015-06-26 15:01             ` Emanuel Berg
2015-06-26 20:25               ` Marcin Borkowski
2015-06-26 22:48                 ` Emanuel Berg
2015-06-27 12:11                 ` Robert Thorpe
2015-06-27 13:12                   ` tomas
2015-06-27 23:02                     ` Emanuel Berg
2015-06-28 11:07                       ` tomas
2015-06-28 15:50                         ` Emanuel Berg
2015-06-28 16:35                           ` Yuri Khan
2015-06-28 20:03                             ` Emanuel Berg
2015-06-28 21:38                           ` Robert Thorpe
2015-06-28 23:47                             ` Emanuel Berg
2015-07-02 23:37                               ` Robert Thorpe
2015-07-03  3:36                                 ` Yuri Khan
2015-07-03  6:41                                   ` Eli Zaretskii
2015-07-03 11:48                                     ` Yuri Khan
2015-07-03 12:16                                       ` Eli Zaretskii
2015-07-03 22:59                                         ` Robert Thorpe
2015-07-03  6:09                                 ` tomas
2015-07-03 19:56                                   ` Emanuel Berg
     [not found]                                 ` <mailman.6215.1435903802.904.help-gnu-emacs@gnu.org>
2015-07-03  6:38                                   ` Rusi
2015-07-03  7:54                                     ` tomas
2015-07-03  8:55                                     ` Loris Bennett
2015-06-24 23:31       ` Emanuel Berg
2015-06-25  2:03       ` Óscar Fuentes
2015-06-25  2:07         ` Emanuel Berg
2015-06-25  2:53           ` Óscar Fuentes
2015-06-25  3:21             ` Emanuel Berg
     [not found]       ` <mailman.5603.1435188769.904.help-gnu-emacs@gnu.org>
2015-06-25  7:43         ` Stefan Nobis
2015-06-25  8:52           ` Andreas Röhler
2015-06-26 14:51             ` Emanuel Berg
2015-06-26 14:39           ` Emanuel Berg
     [not found]           ` <mailman.5719.1435329683.904.help-gnu-emacs@gnu.org>
2015-06-27  7:40             ` Stefan Nobis
2015-06-28  2:02               ` Emanuel Berg
2015-06-28  2:40                 ` Emanuel Berg
     [not found] <mailman.6209.1435880273.904.help-gnu-emacs@gnu.org>
2015-07-03  8:40 ` Pascal J. Bourguignon
2015-07-03 20:04   ` Emanuel Berg

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

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

  git send-email \
    --in-reply-to=558AC4D3.6030509@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --cc=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.