postgresql/src/include/common/string.h

/*
 *	string.h
 *		string handling helpers
 *
 *	Portions Copyright (c) 1996-2017, PostgreSQL Global Development Group
 *	Portions Copyright (c) 1994, Regents of the University of California
 *
 *	src/include/common/string.h
 */
#ifndef COMMON_STRING_H
#define COMMON_STRING_H

extern bool pg_str_endswith(const char *str, const char *end);

#endif							/* COMMON_STRING_H */
Add pg_string_endswith as the start of a string helper library in src/common. Backpatch to 9.3 where src/common was introduce, because a bugfix that needs to be backpatched, requires the function. Earlier branches will have to duplicate the code. 2015-01-03 14:51:52 -05:00			`/*`
			`* string.h`
			`* string handling helpers`
			`*`
Update copyright via script for 2017 2017-01-03 13:48:53 -05:00			`* Portions Copyright (c) 1996-2017, PostgreSQL Global Development Group`
pgindent run for 9.5 2015-05-23 21:35:49 -04:00			`* Portions Copyright (c) 1994, Regents of the University of California`
Add pg_string_endswith as the start of a string helper library in src/common. Backpatch to 9.3 where src/common was introduce, because a bugfix that needs to be backpatched, requires the function. Earlier branches will have to duplicate the code. 2015-01-03 14:51:52 -05:00			`*`
			`* src/include/common/string.h`
			`*/`
			`#ifndef COMMON_STRING_H`
			`#define COMMON_STRING_H`

			`extern bool pg_str_endswith(const char str, const char end);`

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 15:18:54 -04:00			`#endif /* COMMON_STRING_H */`