Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
cmucl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Carl Shapiro
cmucl
Commits
11eeaadd
Commit
11eeaadd
authored
22 years ago
by
toy
Browse files
Options
Downloads
Patches
Plain Diff
Use \textless and \textgreater for < and >, respectively.
parent
2bc7c374
No related branches found
No related tags found
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
docs/cmu-user/compiler-hint.tex
+1
-1
1 addition, 1 deletion
docs/cmu-user/compiler-hint.tex
docs/cmu-user/cross-referencing.tex
+1
-1
1 addition, 1 deletion
docs/cmu-user/cross-referencing.tex
docs/cmu-user/debugger.tex
+2
-2
2 additions, 2 deletions
docs/cmu-user/debugger.tex
with
4 additions
and
4 deletions
docs/cmu-user/compiler-hint.tex
+
1
−
1
View file @
11eeaadd
...
...
@@ -949,7 +949,7 @@ Variables appearing as \code{if} tests are interpreted as
\code
{
=
}
into
\code
{
eql
}
where possible. It is difficult to do
inference directly on
\code
{
=
}
since it does implicit coercions.
When there is an explicit
\code
{
$
<
$
}
or
\code
{
$
>
$
}
test on numeric
When there is an explicit
\code
{
\textless
}
or
\code
{
\textgreater
}
test on numeric
variables, the compiler makes inferences about the ranges the
variables can assume in the true and false branches. This is mainly
useful when it proves that the values are small enough in magnitude to
...
...
This diff is collapsed.
Click to expand it.
docs/cmu-user/cross-referencing.tex
+
1
−
1
View file @
11eeaadd
...
...
@@ -231,7 +231,7 @@ false, and that the first clause of the \code{if} will never be taken
(this optimization is called dead-code elimination). XREF will
therefore not register a call to the function
\code
{
sin
}
from the
function
\code
{
foo
}
. Likewise, no calls to the functions
\code
{
sqrt
}
and
\
verb
|
<
|
are registered, because the compiler has eliminated the
and
\
code
{
\textless
}
are registered, because the compiler has eliminated the
code that evaluates the condition. Finally, no call to the function
\code
{
expt
}
is generated, because the compiler was able to evaluate
the result of the expression
\code
{
(expt 3 2)
}
at compile-time (though
...
...
This diff is collapsed.
Click to expand it.
docs/cmu-user/debugger.tex
+
2
−
2
View file @
11eeaadd
...
...
@@ -230,10 +230,10 @@ values displayed will be the argument values, not values of the
If the variable for an argument is never referenced by the function, it will be
deleted. The variable value is then unavailable, so the debugger prints
\code
{
\#
$
<
$
unused-arg
$
>
$
}
instead of the value. Similarly, if for any of a number of
\code
{
\#
\textless
unused-arg
\textgreater
}
instead of the value. Similarly, if for any of a number of
reasons (described in more detail in section
\ref
{
debug-vars
}
) the value of the
variable is unavailable or not known to be available, then
\code
{
\#
$
<
$
unavailable-arg
$
>
$
}
will be printed instead of the argument value.
\code
{
\#
\textless
unavailable-arg
\textgreater
}
will be printed instead of the argument value.
Printing of argument values is controlled by
\code
{
*debug-print-level*
}
and
\varref
{
debug-print-length
}
.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment