commit 7f5d7b11091dea5b3dd35463891bb0d573ee22be
author gwt.team.scottb <gwt.team.scottb@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Thu Jun 28 18:34:50 2007 +0000
committer gwt.team.scottb <gwt.team.scottb@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Thu Jun 28 18:34:50 2007 +0000
tree a51959317812ffae492c55b27492effd53536a41
parent b6eaae90c7cfcbc2b641459c17c65f4b1d59c8ad

SWT was dealing with VT_BSTR incorrectly.  When marshaling a VT_BSTR from raw system memory into the Variant object, SWT was changing the VT_BSTR to a VT_EMPTY in cases where the data pointer was null.  In fact, this in not correct according to COM rules.  A VT_BSTR with a null data pointer should be treated as an empty string (""), not an empty variant (undefined).

I didn't know this myself, but I found a blog article on this from 2003 that goes into the nuances of BSTRs.

http://blogs.msdn.com/ericlippert/archive/2003/09/12/52976.aspx

Found by: jluis.barrera
Review by: jat (postmortem)


git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@1206 8db76d5a-ed1c-0410-87a9-c151d255dfc7