Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
emacs
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
1
Issues
1
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
emacs
emacs
Commits
3c346cc3
Commit
3c346cc3
authored
Apr 04, 2011
by
Paul Eggert
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
* lread.c (lisp_file_lexically_bound_p, read1): Use unsigned instead of int.
parent
06a0259a
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
3 additions
and
2 deletions
+3
-2
src/ChangeLog
src/ChangeLog
+1
-0
src/lread.c
src/lread.c
+2
-2
No files found.
src/ChangeLog
View file @
3c346cc3
2011-04-04 Paul Eggert <eggert@cs.ucla.edu>
* lread.c (lisp_file_lexically_bound_p): Use ints rather than endptrs.
(lisp_file_lexically_bound_p, read1): Use unsigned instead of int.
* print.c (print_error_message): Avoid int overflow.
src/lread.c
View file @
3c346cc3
...
...
@@ -819,7 +819,7 @@ lisp_file_lexically_bound_p (Lisp_Object readcharfun)
while
(
in_file_vars
)
{
char
var
[
100
],
val
[
100
];
int
i;
unsigned
i
;
ch
=
READCHAR
;
...
...
@@ -2319,7 +2319,7 @@ static Lisp_Object
read1
(
register
Lisp_Object
readcharfun
,
int
*
pch
,
int
first_in_list
)
{
register
int
c
;
int
uninterned_symbol = 0;
unsigned
uninterned_symbol
=
0
;
int
multibyte
;
*
pch
=
0
;
...
...
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