#
5e3934b1 |
| 24-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
usr.bin: Automated cleanup of cdefs and other formatting
Apply the following automated changes to try to eliminate no-longer-needed sys/cdefs.h includes as well as now-empty blank lines in a row.
R
usr.bin: Automated cleanup of cdefs and other formatting
Apply the following automated changes to try to eliminate no-longer-needed sys/cdefs.h includes as well as now-empty blank lines in a row.
Remove /^#if.*\n#endif.*\n#include\s+<sys/cdefs.h>.*\n/ Remove /\n+#include\s+<sys/cdefs.h>.*\n+#if.*\n#endif.*\n+/ Remove /\n+#if.*\n#endif.*\n+/ Remove /^#if.*\n#endif.*\n/ Remove /\n+#include\s+<sys/cdefs.h>\n#include\s+<sys/types.h>/ Remove /\n+#include\s+<sys/cdefs.h>\n#include\s+<sys/param.h>/ Remove /\n+#include\s+<sys/cdefs.h>\n#include\s+<sys/capsicum.h>/
Sponsored by: Netflix
show more ...
|
#
bdcbfde3 |
| 23-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
usr.bin: Remove ancient SCCS tags.
Remove ancient SCCS tags from the tree, automated scripting, with two minor fixup to keep things compiling. All the common forms in the tree were removed with a pe
usr.bin: Remove ancient SCCS tags.
Remove ancient SCCS tags from the tree, automated scripting, with two minor fixup to keep things compiling. All the common forms in the tree were removed with a perl script.
Sponsored by: Netflix
show more ...
|
Revision tags: release/14.0.0 |
|
#
1d386b48 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line .c pattern
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0 |
|
#
5088a2d1 |
| 21-May-2020 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): add fallthrough markers
This silences -Wimplicit-fallthrough warnings.
Submitted by: Michael Paquier Obtained from: postgresql.org MFC after: 3 days
|
#
02bde5cf |
| 07-Apr-2020 |
Kyle Evans <kevans@FreeBSD.org> |
indent: fix the -fno-common build
Spread the globals far and wide, hopefully to the files that make the most sense.
-fno-common will become the default in GCC10/LLVM11.
MFC after: 3 days
|
Revision tags: release/12.1.0, release/11.3.0, release/12.0.0 |
|
#
c06e7b66 |
| 07-Nov-2018 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r340126 through r340212.
|
#
377421df |
| 04-Nov-2018 |
Mariusz Zaborski <oshogbo@FreeBSD.org> |
capsicum: use a new capsicum helpers in tools
Use caph_{rights,ioctls,fcntls}_limit to simplify the code.
|
#
01c66110 |
| 16-Jul-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): rewrite the integer/floating constant scanning part of lexi.c
Remove procedural code that did the scanning, which was faulty and didn't support complex constants such as 0x1p-61. Replace
indent(1): rewrite the integer/floating constant scanning part of lexi.c
Remove procedural code that did the scanning, which was faulty and didn't support complex constants such as 0x1p-61. Replace it with a finite state machine expressed as a transition table. The table was rewritten by hand from lx's output, given parts of grammar expressed as regular expressions.
lx is Katherine Flavel's lexer generator, currently available at https://github.com/katef/libfsm and the parts of grammar were taken from http://quut.com/c/ANSI-C-grammar-l-2011.html and extended to support binary integer constants which are a popular GCC extension.
Reported by: bde
show more ...
|
Revision tags: release/11.2.0 |
|
#
7672a014 |
| 20-Jun-2018 |
Mariusz Zaborski <oshogbo@FreeBSD.org> |
Convert `cap_enter() < 0 && errno != ENOSYS` to `caph_enter() < 0`.
No functional change intended.
|
#
7e53aaed |
| 10-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): group global option variables into an options structure
It's clearer now when a variable represents a toggable command line option.
Many options were stored in the parser's state structu
indent(1): group global option variables into an options structure
It's clearer now when a variable represents a toggable command line option.
Many options were stored in the parser's state structure, so fix also that.
show more ...
|
#
4d0c6228 |
| 04-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): remove static const char copyright[]
It repeats what is already said in the heading comment and it's optimized out so serves no purpose.
|
#
03e6aeef |
| 04-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): replace BSD bcopy() with C memmove()
|
#
aac30b75 |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): new option -lpl
With -lpl, code surrounded by parentheses in continuation lines is lined up even if it would extend past the right margin.
With -nlpl (the default), such a line that woul
indent(1): new option -lpl
With -lpl, code surrounded by parentheses in continuation lines is lined up even if it would extend past the right margin.
With -nlpl (the default), such a line that would extend past the right margin is moved left to keep it within the margin, if that does not require placing it to the left of the prevailing indentation level.
These switches have no effect if -nlp is selected.
Submitted by: Tom Lane
show more ...
|
#
50a29760 |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): revert introduction of -lpl
That was committed with the wrong message. Will be re-added.
|
#
971e1c47 |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): new option -lpl (always line up to parenthesis)
With -lp, if a line has an opening paren which is not closed on that line, then continuation lines will be lined up to start at the charact
indent(1): new option -lpl (always line up to parenthesis)
With -lp, if a line has an opening paren which is not closed on that line, then continuation lines will be lined up to start at the character position just after the opening paren.
Submitted by: Tom Lane
show more ...
|
#
01a206e6 |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): if the token is a "[" then neither of the blocks is relevant
|
#
fa7ea0c9 |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): don't add a space after a label
It's not needed and it fools pr_comment().
|
#
370d0cf9 |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): don't overflow di_stack[]
|
#
9de29bfb |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): improve CHECK_SIZE_ macros
Rewrite the macros so that they take a parameter. Consumers use it to signal how much room in the buffer they need; this lets them do that once when required sp
indent(1): improve CHECK_SIZE_ macros
Rewrite the macros so that they take a parameter. Consumers use it to signal how much room in the buffer they need; this lets them do that once when required space is known instead of doing the check once every loop step.
Also take the parameter value into consideration when resizing the buffer; the requested space may be larger than the constant 400 bytes that the previous version used - now it's the sum of those two values.
On the consumer side, don't copy strings byte by byte - use memcpy().
Deduplicate code that copied base 2, base 8 and base 16 literals.
Don't advance the e_token pointer once the token has been copied into s_token. This allows easy calculation of the token's length.
show more ...
|
#
1479f36d |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): remove troff output support
The troff output in indent was invented at Sun and the online documentation for some post-SunOS operating system includes this: The usual way to get a troff
indent(1): remove troff output support
The troff output in indent was invented at Sun and the online documentation for some post-SunOS operating system includes this: The usual way to get a troffed listing is with the command indent -troff program.c | troff -mindent
The indent manual page in FreeBSD 1.0 already lacks that information and troff -mindent complains about not being able to find the macro file. It seems that the file did exist on SunOS and was supposed to be imported into 4.3BSD together with the feature, but that has never happened.
Removal of troff output support simplifies a lot of indent's code.
vgrind(1) seems to be a promising replacement.
show more ...
|
#
bef613ff |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): the check for buffer overflow has to be done before copy
|
#
33c24642 |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): use errx() instead of abort()
|
#
e1baf57e |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): limit character classification functions' input to unsigned char
|
#
9522d0b0 |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): don't format function declarations as variables
|
#
e95d1e3c |
| 03-Jun-2018 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
indent(1): remove is_procname.
It was a shorthand for checking if ps.procname is a non-empty string; the same can be done with ps.procname[0] which avoids the need for updating is_procname after eve
indent(1): remove is_procname.
It was a shorthand for checking if ps.procname is a non-empty string; the same can be done with ps.procname[0] which avoids the need for updating is_procname after every call to lexi().
show more ...
|