[Boost-users] Re: [BGL][variant] variant as internal edge property -nastiness w/MS7.1 + 1.31.0

From: Christopher D. Russell (cdr_at_[hidden])
Date: 2004-12-15 17:46:13

Yea - this one really caught me by surprise as well. I'm expecting to 
complete this 1.31.0-based work within the next few days and plan to grab 
1.32.0 release and have another go at it. I'll write it up my results and 
post some sample code.

- Regards
Chris

"Doug Gregor" <dgregor_at_[hidden]> wrote in message 
news:EDDF7620-4ED8-11D9-A4F6-000A95B0EC64_at_cs.indiana.edu...
> On Dec 10, 2004, at 9:38 AM, Christopher D. Russell wrote:
>
>> This isn't a question but rather a quick report for my future reference - 
>> I
>> need to circle back and try to characterize this problem more fully when 
>> I'm
>> not on deadline and can run some additional tests with Boost 1.32.0.
>>
>> Environment:
>>
>> - MS 7.1 compiler w/their STL distribution
>> - Boost 1.31.0 (my client doesn't want to update to 1.32.0 until after 
>> this
>> release)
>>
>> Summary:
>>
>> boost::variant registered as an internal edge property map member on a BGL
>> graph causes the resultant graph to be inaccessible due to what appears to 
>> be
>> incorrect initialization of both the internal vertex and edge property 
>> maps.
>> I SUSPECT THAT THE ROOT CAUSE OF THIS CAN BE TRACKED BACK TO A MS 7.1
>> COMPILER BUG due to the fact that attempts to compile my test code results 
>> in
>> either of (a) an C1001 Internal Compiler Error (b) a error-free compile 
>> and a
>> completely screwed runtime.
>
> That's really strange... we've never come across any initialization 
> problems (on any platform) with these, especially because the internal 
> properties are just stored in lists or vectors most of the time... nothing 
> fancy going on there.
>
> I would appreciate if you could check with 1.32.0 and if you're still 
> running into the problem we'll see if we can duplicate it and come up with 
> a workaround.
>
> Doug