database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Update workding on why we use is_absolute_path() as a macro.

Browse Source
This commit is contained in:
Bruce Momjian
2004-11-08 16:34:23 +00:00
parent 4b3a2d854c
commit 9d95cdcb07
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/include/port.h
View File

@ -6,7 +6,7 @@
* Portions Copyright (c) 1996-2004, PostgreSQL Global Development Group * Portions Copyright (c) 1996-2004, PostgreSQL Global Development Group
* Portions Copyright (c) 1994, Regents of the University of California * Portions Copyright (c) 1994, Regents of the University of California
* *
* $PostgreSQL: pgsql/src/include/port.h,v 1.65 2004/11/06 01:16:14 tgl Exp $ * $PostgreSQL: pgsql/src/include/port.h,v 1.66 2004/11/08 16:34:23 momjian Exp $
* *
*------------------------------------------------------------------------- *-------------------------------------------------------------------------
*/ */
@ -47,9 +47,8 @@ extern void get_parent_directory(char *path);
/* /*
* is_absolute_path * is_absolute_path
* *
* This capability is needed by libpq and initdb.c * By making this a macro we prevent the need for libpq to include
* On Win32, you can't reference the same object file that is * path.c which uses exec.c.
* in two different libraries (pgport and libpq), so a macro is best.
*/ */
#ifndef WIN32 #ifndef WIN32
#define is_absolute_path(filename) \ #define is_absolute_path(filename) \