Re: MS VC++ 6 issues

[Roger H. <rog...@mi...>]

I don't know what  the actual message from the compiler was, but maybe 
it was tying itself in knots
thinking that the refID field was being set to itself rather than a 
variable of the same name.
Just a hunch, I don't use the windows C++ compiler.

Making a class its own friend seems pointless, and as you say, bizarre. 
Anyway that class will be
merged into OpaqueTQ3Object in a couple of weeks if all goes well.

Roger.



On Monday, January 17, 2005, at 08:23  pm, James W. Walker wrote:

> I guess I can get used to not using the and, or, and not keywords, 
> maybe they're not standard.  Making a class a friend to itself is 
> bizarre, but maybe it won't come up too often.  I'm really worried 
> about the change below.  What was the compiler complaining about?  
> Looks like standard C++ to me, and certainly seems to be permitted 
> according to sections 8.5.1 and 12.6.1 of the 1998 C++ standard.
>
>> *** 939,947 ****
>>   					if (labelIter != instanceData->mLabelMap->end())
>>   					{
>> ! 						TOCEntry	tocEntry = {
>> ! 							refID,
>> ! 							labelIter->second,
>> ! 							CQ3ObjectRef()
>> ! 						};
>>   						instanceData->mTOC->push_back( tocEntry );
>>   					}
>> --- 939,948 ----
>>   					if (labelIter != instanceData->mLabelMap->end())
>>   					{
>> ! 						TOCEntry	tocEntry;
>> ! 						
>> ! 						tocEntry.refID = refID;
>> ! 						tocEntry.objLocation = labelIter->second;
>> ! 						tocEntry.object = CQ3ObjectRef();
>> ! 						
>
> --
> <http://www.jwwalker.com/>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Quesa-develop mailing list
> Que...@li...
> https://lists.sourceforge.net/lists/listinfo/quesa-develop
>