Skip site navigation (1) Skip section navigation (2)

[Keystone Slip # 17] Nameclash between PG and MS ERROR macros

From: webmaster(at)postgreSQL(dot)org
To: pgsql-bugs(at)postgreSQL(dot)org
Subject: [Keystone Slip # 17] Nameclash between PG and MS ERROR macros
Date: 1999-07-26 16:44:10
Message-ID: 199907261644.MAA11125@hub.org (view raw or flat)
Thread:
Lists: pgsql-bugs
---------------------------------------------------------------------------
Slip number -----: 17
Problem ---------: Nameclash between PG and MS ERROR macros
Opened by -------: goran(dot)lowkrantz(at)infologigruppen(dot)se on 07/25/99 21:28
Assigned To -----: momjian
---------------------------------------------------------------------------
Summary:
System: WinNT 4.0SP5 MSVC 6.0SP2 PostgreSQL 6.5.1

Compiling the Win32 frontend, the macro ERROR defined in src/include/utils/elog.h, line 17, value -1, is overwritten by a macro in wingdi.h, line 93, value 0, so that the PG ERROR code is the same as a PG NOTIFY code.

Suggestion: Change ERROR and the rest to somthing like PG_ERROR.
 
---------------------------------------------------------------------------
History:
07/26/99 12:44 by scrappy:
Dependency changed to 0 from 
Current tech changed to momjian from 
Status changed to O from U
Contact changed to  from ANONYMOUS
Scheduled Close Date changed to 0 from 
Scheduled Open Date changed to 0 from 
Public setting changed to 1 from 0
Policy changed to 0

---------------------------------------------------------------------------


          Full information on this slip is available at:
http://www.postgresql.org/bugs/visitor.php3?sid=17&v_func=zoom

---------------------------------------------------------------------------
This message was generated automatically by Keystone at http://www.postgresql.org


pgsql-bugs by date

Next:From: webmasterDate: 1999-07-26 16:44:58
Subject: [Keystone Slip # 21] Compilation problems under Linux
Previous:From: webmasterDate: 1999-07-26 16:43:39
Subject: [Keystone Slip # 16] pg_dump, psql CURRENT_DATE problems

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group