all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Andreas Röhler'" <andreas.roehler@easy-emacs.de>,
	help-gnu-emacs@gnu.org
Cc: 'Stefan Monnier' <monnier@IRO.UMontreal.CA>
Subject: RE: Avoiding 'reference to free variable' warningswhilesplittingelisp source files
Date: Sun, 24 Mar 2013 07:34:58 -0700	[thread overview]
Message-ID: <1E2C13C6E7944065A290F6A90160273D@us.oracle.com> (raw)
In-Reply-To: <514EC11C.6020203@easy-emacs.de>

> At the very case, as we may and must make an agreement how to 
> understand words, IMO Stefan's proposal is useful.
> 
> What about to understand "define" in a wider sense, making 
> more comprehensive assigments, while "declare" is understood
> as a beginning of a defining-process, undertaking its
> initial part.
> 
> Probably "initiate" would be es good a "declare", it's just 
> to agree a convention, a possibility.

Sorry, I don't have anything particular to add to what I already wrote.

As I said, I have no great objection to a replacement of "define/definition"
everywhere" by "declare/declaration", if done consistently and with attention.
It is tilting at windmills IMO, but go for it if you think it improves
something.

But see what I wrote earlier for a more nuanced response.
If what I've written doesn't help you, please ignore it.




      reply	other threads:[~2013-03-24 14:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-23 16:08 Avoiding 'reference to free variable' warnings while splitting elisp source files Joe Riel
2013-03-23 16:19 ` Avoiding 'reference to free variable' warnings while splittingelisp " Drew Adams
2013-03-23 17:30   ` Stefan Monnier
2013-03-23 18:23     ` Avoiding 'reference to free variable' warnings whilesplittingelisp " Drew Adams
2013-03-23 21:05       ` Stefan Monnier
2013-03-23 22:41         ` Avoiding 'reference to free variable' warningswhilesplittingelisp " Drew Adams
2013-03-24  9:02           ` Andreas Röhler
2013-03-24 14:34             ` Drew Adams [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

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

  git send-email \
    --in-reply-to=1E2C13C6E7944065A290F6A90160273D@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=andreas.roehler@easy-emacs.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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.