unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Daniel Martín" <mardani29@yahoo.es>
To: Jean Louis <bugs@gnu.support>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to avoid warning, with undefined functions in a package
Date: Mon, 19 Oct 2020 10:34:59 +0200	[thread overview]
Message-ID: <m1imb67gwc.fsf@yahoo.es> (raw)
In-Reply-To: <courier.000000005F8D2AF5.00001EFE@static.rcdrun.com> (Jean Louis's message of "Mon, 19 Oct 2020 08:58:11 +0300")

Jean Louis <bugs@gnu.support> writes:

> Let us say I have some speech functions, but do not want to
> (require 'festival) for the package rcd-utilities.el
>
> Those are undefined functions and variables, but I would not like
> defining them, or requiring them, unless user has that other package.
>
> What would be good approach to solve that, and that there are no
> compiler warnings?
>
> In rcd-speak-festival:
> rcd-utilities.el:121:23: Warning: reference to free variable
>     ‘festival-program-name’
>
> In end of data:
> rcd-utilities.el:205:1: Warning: the function ‘festival-say-string’ is not
>     known to be defined.

There are several possible techniques. The Elisp manual explains some of
them:

C-h i m Elisp RET i byte-compiler warnings RET



  reply	other threads:[~2020-10-19  8:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19  5:58 How to avoid warning, with undefined functions in a package Jean Louis
2020-10-19  8:34 ` Daniel Martín [this message]
2020-10-19 15:16 ` Drew Adams
2020-10-19 17:57   ` Jean Louis
2020-10-19 18:33     ` Emanuel Berg via Users list for the GNU Emacs text editor

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=m1imb67gwc.fsf@yahoo.es \
    --to=mardani29@yahoo.es \
    --cc=bugs@gnu.support \
    --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.
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).