Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
7
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
5bb0cda3
Commit
5bb0cda3
authored
Nov 24, 2007
by
Glenn Morris
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
(Compiler Errors): Mention declaring functions, defvar with no
initvalue, and byte-compile-warnings.
parent
e31dfb12
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
15 additions
and
0 deletions
+15
-0
doc/lispref/ChangeLog
doc/lispref/ChangeLog
+6
-0
doc/lispref/compile.texi
doc/lispref/compile.texi
+9
-0
No files found.
doc/lispref/ChangeLog
View file @
5bb0cda3
2007
-
11
-
24
Glenn
Morris
<
rgm
@
gnu
.
org
>
*
functions
.
texi
(
Declaring
Functions
):
New
section
.
*
compile
.
texi
(
Compiler
Errors
):
Mention
declaring
functions
,
defvar
with
no
initvalue
,
and
byte
-
compile
-
warnings
.
2007
-
11
-
15
Martin
Rudalics
<
rudalics
@
gmx
.
at
>
*
vol1
.
texi
(
Top
):
Remove
Frame
-
Local
Variables
from
Node
Listing
.
...
...
doc/lispref/compile.texi
View file @
5bb0cda3
...
...
@@ -505,6 +505,9 @@ The call to @var{func} must be in the @var{then-form} of the
@code{if}, and @var{func} must appear quoted in the call to
@code{fboundp}. (This feature operates for @code{cond} as well.)
You can tell the compiler that a function is defined using a
@code{declare-function} statement (@pxref{Declaring Functions}).
Likewise, you can suppress a compiler warning for an unbound variable
@var{variable} by conditionalizing its use on a @code{boundp} test,
like this:
...
...
@@ -518,6 +521,9 @@ The reference to @var{variable} must be in the @var{then-form} of the
@code{if}, and @var{variable} must appear quoted in the call to
@code{boundp}.
You can tell the compiler that a variable is defined using a
@code{defvar} statement with no initial value.
You can suppress any compiler warnings using the construct
@code{with-no-warnings}:
...
...
@@ -533,6 +539,9 @@ We recommend that you use this construct around the smallest
possible piece of code.
@end defspec
More precise control of warnings is possible by setting the variable
@code{byte-compile-warnings}.
@node Byte-Code Objects
@section Byte-Code Function Objects
@cindex compiled function
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment