2014-02-15 20:31:30 +01:00
|
|
|
/*
|
|
|
|
* Portions Copyright (c) 1987, 1993, 1994
|
|
|
|
* The Regents of the University of California. All rights reserved.
|
|
|
|
*
|
2017-01-03 19:48:53 +01:00
|
|
|
* Portions Copyright (c) 2003-2017, PostgreSQL Global Development Group
|
2014-02-15 20:31:30 +01:00
|
|
|
*
|
|
|
|
* src/include/pg_getopt.h
|
|
|
|
*/
|
|
|
|
#ifndef PG_GETOPT_H
|
|
|
|
#define PG_GETOPT_H
|
|
|
|
|
|
|
|
/* POSIX says getopt() is provided by unistd.h */
|
|
|
|
#include <unistd.h>
|
|
|
|
|
|
|
|
/* rely on the system's getopt.h if present */
|
|
|
|
#ifdef HAVE_GETOPT_H
|
|
|
|
#include <getopt.h>
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If we have <getopt.h>, assume it declares these variables, else do that
|
|
|
|
* ourselves. (We used to just declare them unconditionally, but Cygwin
|
|
|
|
* doesn't like that.)
|
|
|
|
*/
|
|
|
|
#ifndef HAVE_GETOPT_H
|
|
|
|
|
|
|
|
extern char *optarg;
|
|
|
|
extern int optind;
|
|
|
|
extern int opterr;
|
|
|
|
extern int optopt;
|
|
|
|
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-21 21:18:54 +02:00
|
|
|
#endif /* HAVE_GETOPT_H */
|
2014-05-08 18:33:29 +02:00
|
|
|
|
|
|
|
/*
|
2014-05-08 18:42:56 +02:00
|
|
|
* Some platforms have optreset but fail to declare it in <getopt.h>, so cope.
|
|
|
|
* Cygwin, however, doesn't like this either.
|
2014-05-08 18:33:29 +02:00
|
|
|
*/
|
|
|
|
#if defined(HAVE_INT_OPTRESET) && !defined(__CYGWIN__)
|
2014-02-15 20:31:30 +01:00
|
|
|
extern int optreset;
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#ifndef HAVE_GETOPT
|
2017-06-21 20:39:04 +02:00
|
|
|
extern int getopt(int nargc, char *const *nargv, const char *ostr);
|
2014-02-15 20:31:30 +01:00
|
|
|
#endif
|
|
|
|
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-21 21:18:54 +02:00
|
|
|
#endif /* PG_GETOPT_H */
|