Re: [Boost-users] Could the BGL graph algorithms be improvedtoautomatically work with VertexList = listS graphs?

From: Tony Cook (tony__cook_at_[hidden])
Date: 2005-09-15 14:23:54

>>Ew, that doesn't sound right. What graph type was that with? Could
>>you send a little program that demonstrates the problem.

OK scrub that problem (blush) - it was mine - one of my property values 
shallow copied when it shouldn't have

>Ugh, I thought our days of ICE's from VC was over... that brings back
>bad memories from the days of VC 6.

I can post the exact details when I'm back at work tomorrow but it occurs 
somewere in MPLs /plain/apply_wrap.hpp which I presume the BGL is using 
indirectly. I've done some tracing as the interesting thing is that the 
/plain/ version was selected and not the /msvc60/ or /msvc70/  versions of 
apply_wrap.hpp.  The crux is I can see some conditional compilation in the 
MPL that knows about VC6.0 and VC7.0 but it is *unaware* of VC7.1 and thus 
selects the /plain/ version (maybe intentionally) - however VC7.1 chokes in 
certain combinations of graph type/property types.There is no /msvc71/ 
compiler specific stuff in MPL, is VC7.1 requiring no workarounds?

This is scaring the hell out of me as adding new vertex or edge properties 
is apt to trip an ICE, as is changing the graph VertexList and EdgeList 
types. I've been lucky in that reordering the property type nests has so far 
cured the prob - but for how much longer - the combination to try are 
growing - and property bundles are also ICE tripping.

I've done the obvious and tried fooling boost into thinking its being 
compiled under VC7.0 but I haven't succeded yet.

Tony