unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: How do I clean up "might not be defined" wrnings?
Date: Fri, 21 Nov 2014 23:14:45 +0100	[thread overview]
Message-ID: <m34mts5hgq.fsf@stories.gnus.org> (raw)
In-Reply-To: <20141121192849.B55E1382F6B@snark.thyrsus.com> (unknown@unknown.invalid's message of "Fri, 21 Nov 2014 14:28:49 -0500 (EST)")

Unknown <unknown@unknown.invalid> writes:

> I've started a significant refactoring and simplification of the VC
> code. This has involved moving functions to different files, which
> is causing "functions might not be defined" warnings.
>
> What is the approved way to prevent these or clean them up?

You should structure this so that you can require the files providing
the functions from the files that need them.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



      parent reply	other threads:[~2014-11-21 22:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 19:28 How do I clean up "might not be defined" wrnings? Unknown
2014-11-21 21:58 ` Tassilo Horn
2014-11-21 22:03   ` Eric S. Raymond
2014-11-22  5:53     ` Stephen J. Turnbull
2014-11-21 22:14 ` Lars Magne Ingebrigtsen [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=m34mts5hgq.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@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 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).