Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commite550763

Browse files
committed
Improve comment about 'if (1)' hack in copy.c macros.
1 parent1a0ebe6 commite550763

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

‎src/backend/commands/copy.c

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
*
99
*
1010
* IDENTIFICATION
11-
* $PostgreSQL: pgsql/src/backend/commands/copy.c,v 1.310 2009/06/0314:48:33 momjian Exp $
11+
* $PostgreSQL: pgsql/src/backend/commands/copy.c,v 1.311 2009/06/0315:06:48 tgl Exp $
1212
*
1313
*-------------------------------------------------------------------------
1414
*/
@@ -175,11 +175,13 @@ typedef struct
175175
/*
176176
* These macros centralize code used to process line_buf and raw_buf buffers.
177177
* They are macros because they often do continue/break control and to avoid
178-
* function call overhead in tight COPY loops. "((void) 0)" is used to silence
179-
* compiler warnings.
178+
* function call overhead in tight COPY loops.
180179
*
181-
* We must use "if (1)" because "do {} while(0)" overrides the continue/break
182-
* processing.See http://www.cit.gu.edu.au/~anthony/info/C/C.macros.
180+
* We must use "if (1)" because the usual "do {...} while(0)" wrapper would
181+
* prevent the continue/break processing from working. We end the "if (1)"
182+
* with "else ((void) 0)" to ensure the "if" does not unintentionally match
183+
* any "else" in the calling code, and to avoid any compiler warnings about
184+
* empty statements. See http://www.cit.gu.edu.au/~anthony/info/C/C.macros.
183185
*/
184186

185187
/*

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp