Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 1a0ebe6

Browse files
committed
Add comment about why "((void) 0)" is used in copy macros.
1 parent 44ead23 commit 1a0ebe6

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

src/backend/commands/copy.c

Lines changed: 3 additions & 2 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.309 2009/05/29 13:54:52 meskes Exp $
11+
* $PostgreSQL: pgsql/src/backend/commands/copy.c,v 1.310 2009/06/03 14:48:33 momjian Exp $
1212
*
1313
*-------------------------------------------------------------------------
1414
*/
@@ -175,7 +175,8 @@ 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.
178+
* function call overhead in tight COPY loops. "((void) 0)" is used to silence
179+
* compiler warnings.
179180
*
180181
* We must use "if (1)" because "do {} while(0)" overrides the continue/break
181182
* processing. See http://www.cit.gu.edu.au/~anthony/info/C/C.macros.

0 commit comments

Comments
 (0)