Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://www.gnu.org/software/emacs/manual/html_node/elisp/Warning-Tips.html below:

Warning Tips (GNU Emacs Lisp Reference Manual)

Next: Tips for Documentation Strings, Previous: Tips for Making Compiled Code Fast, Up: Tips and Conventions   [Contents][Index]

• Try to avoid compiler warnings about undefined free variables, by adding dummy defvar definitions for these variables, like this:

  Such a definition has no effect except to tell the compiler not to warn about uses of the variable foo in this file.

• Similarly, to avoid a compiler warning about an undefined function that you know will be defined, use a declare-function statement (see Telling the Compiler that a Function is Defined).
• If you use many functions, macros, and variables from a certain file, you can add a require (see require) for that package to avoid compilation warnings for them, like this:

  If you need only macros from some file, you can require it only at compile time (see Evaluation During Compilation). For instance,

  (eval-when-compile
    (require 'foo))
  

• If you bind a variable in one function, and use it or set it in another function, the compiler warns about the latter function unless the variable has a definition. But adding a definition would be unclean if the variable has a short name, since Lisp packages should not define short variable names. The right thing to do is to rename this variable to start with the name prefix used for the other functions and variables in your package.
• The last resort for avoiding a warning, when you want to do something that is usually a mistake but you know is not a mistake in your usage, is to put it inside with-no-warnings. See Compiler Errors.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4