| Age | Commit message (Collapse) | Author |
|
|
|
Since all command line options modify a member of struct options, there
is no need to encode that relocation 38 times.
No functional change.
|
|
|
|
|
|
No binary change.
|
|
No functional change.
|
|
No functional change.
|
|
Taken from share/misc/indent.pro.
Indent does not wrap code to fit into the line width, it only does so
for comments. The 'INDENT OFF' sections and too long lines will be
addressed in a follow-up commit.
No functional change.
|
|
|
|
|
|
No functional change.
|
|
|
|
|
|
|
|
No functional change.
|
|
|
|
In struct pro, place the dependent member below its dependency.
In load_profile, consistently use -1 when outside a comment.
No functional change.
|
|
Initialize buffers in reading order, make comments more expressive,
rename add_typename to register_typename, remove unused macro.
No functional change.
|
|
Previously, on an ILP32 platform, the option '-ts30000000000000000'
resulted in the error message 'must be an integer', on LP64 platforms it
resulted in the error message 'must be between 1 and 80'. Remove this
unnecessary difference.
|
|
No functional change.
|
|
At this early time, the input file has not been opened yet, so there is
no reason to output either the input file name or the line number.
|
|
|
|
|
|
No functional change.
|
|
NetBSD's indent has deviated enough from FreeBSD's indent to warrant a
different product name. When indent was copied from FreeBSD in 2019,
that update introduced several new bugs, some of which have been fixed
in the NetBSD version.
NetBSD indent, unlike FreeBSD indent, supports C99 comments and C99
initializer designators.
|
|
With manual corrections afterwards, to compensate for the remaining bugs
in indent.
Without the type definitions in .indent.pro, the opening braces of the
functions kw_name and lexi_alnum would not be at the beginning of the
line.
|
|
With manual corrections afterwards. Indent still does not get
extra_expr_indent correctly, it also indents global variables after
tagged declarations too deep.
No functional change.
|
|
|
|
|
|
On i386 and other platforms where LONG_MAX == INT_MAX, the test
t_errors/option_tabsize_very_large failed since the behavior on integer
overflow differs between ILP32 and LP64 platforms. Noticed by gson@.
Avoid this unintended difference by adding reasonable limits for each of
the integer options and by replacing atoi with strtol.
|
|
Previously, bool options were allowed to have trailing garbage. For
example, the option '-bacc' could be spelled '-bacchus' as well.
Check that the exact option name is given in the command line, to
prevent typos in the configuration files and to reduce surprises just in
case a future option is a prefix of an existing option, or vice versa.
Add a new test program for error handling. Most of these tests are so
simple that it would be overkill to create 3 files for each test.
|
|
Sort the macros, remove redundancy from comment.
Remove redundant lint comment. Lint still does not recognize
__attribute__((__noreturn__)), but it also doesn't perform advanced
control flow analysis, so there is no point in having the comment, as it
doesn't suppress any warnings.
No functional change.
|
|
No functional change.
|
|
The formatting looks mostly OK.
Some struct members had excessively long names, leaving no space for
their corresponding comments. Renamed some of them using well-known
abbreviations.
The formatting for debug_vis_range is messed up, no idea why. It is
clearly a function declaration, not a function definition, so there is
no need to place the function name in column 1.
No functional change.
|
|
No functional change.
|
|
No functional change.
|
|
It is only needed at startup, while parsing the options. The string "?"
was not needed at all.
No functional change.
|
|
|
|
|
|
|
|
When reading a comment in a profile file, don't store the characters of
the comment in the buffer, just skip them. This allows for long comments
without triggering overflow errors.
|
|
|
|
No functional change.
|
|
No functional change.
|
|
There was no good reason for using the different verbs 'scan' and 'set'
for two functions that essentially do the same.
No functional change.
|
|
Previously, profile_name included the leading "-P", which was confusing.
|
|
No functional change.
|
|
No functional change.
|
|
Almost all boolean options are negatable, so model this directly instead
of saving each option twice. This saves memory, is faster and more
directly models reality.
No functional change.
|
|
No functional change.
|