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

Re: [HACKERS] Patch for VS.Net 2005's strxfrm() bug

From: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
To: <pgsql-hackers(at)postgresql(dot)org>,"William ZHANG" <uniware(at)zedware(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Patch for VS.Net 2005's strxfrm() bug
Date: 2006-07-25 16:30:23
Message-ID: 012401c6b007$a1480870$01324d80@hiroshi5jz7dqj (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Hi.

"William ZHANG" <uniware(at)zedware(dot)org> wrote in message news:ea5fm1$2q6i$1(at)news(dot)hub(dot)org(dot)(dot)(dot)
> When I tried to compile pgsql-8.2devel with VS.Net 2005 and do regression 
> tests,
> I found the problem. It's a bug inVS.Net 2005:
> http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=99694
> 

+   /* http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=99694 */
+ #if _MSC_VER == 1400
+   {
+    char x[1];
+ 
+    xfrmlen = strxfrm(x, val, 0);
+   }
+ #else
    xfrmlen = strxfrm(NULL, val, 0);
+ #endif


Hmm, It seems to be the bug of very unpleasant Microsoft.:D
I think that the following is desirable as an evasion measure to add. 

#if defined(_MSC_VER) && _MSC_VER == 1400

To be sure, it was only VS2005.

Regards,
Hiroshi Saito


In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-07-25 16:30:53
Subject: Re: Forcing current WAL file to be archived
Previous:From: Tom LaneDate: 2006-07-25 16:29:47
Subject: Re: Forcing current WAL file to be archived

pgsql-patches by date

Next:From: Bernd HelmleDate: 2006-07-25 16:31:32
Subject: Patch for updatable views
Previous:From: Tom LaneDate: 2006-07-25 16:18:38
Subject: Re: Patch for VS.Net 2005's strxfrm() bug

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