Home > Archive > VC STL > April 2005 > issues with list and queue classes
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
issues with list and queue classes
|
|
| schapparam 2005-03-14, 2:36 pm |
| We found issues with MS STL version 6.0 with STL container classes. Want to know if they are resolved now in VC .NET 2003?
thanks in advance,
Sucharitha | |
| Carl Daniel [VC++ MVP] 2005-03-14, 9:00 pm |
| schapparam wrote:
> We found issues with MS STL version 6.0 with STL container classes.
> Want to know if they are resolved now in VC .NET 2003?
Such as?
Have you looked at the patches for VC6 (and VC5) STL at
http://www.dinkumware.com/vc_fixes.html
?
-cd
| |
| Tom Widmer 2005-03-15, 9:01 am |
| schapparam wrote:
> We found issues with MS STL version 6.0 with STL container classes. Want
> to know if they are resolved now in VC .NET 2003?
Well, std::list in VC6 has a restricted interface (no templated sort
member, for example), but as long as you applied the patches Carl has
mentioned, it does work AFAIK. What were the issues?
However, VC.NET 2003 does have a much higher quality library
implementation (from the same vendor), with only a few obscure bugs, and
no unarguable compliance issues that I know of.
Tom
| |
| Felipe Magno de Almeida 2005-03-15, 4:02 pm |
| Tom Widmer wrote:
> schapparam wrote:
>
>
>
> Well, std::list in VC6 has a restricted interface (no templated sort
> member, for example), but as long as you applied the patches Carl has
> mentioned, it does work AFAIK. What were the issues?
>
> However, VC.NET 2003 does have a much higher quality library
> implementation (from the same vendor), with only a few obscure bugs, and
> no unarguable compliance issues that I know of.
>
> Tom
What kind of obscure bugs? is there any page saying anything about it?
--
Felipe Magno de Almeida
UIN: 2113442
email: felipe.almeida at ic unicamp br, felipe.m.almeida at gmail
com, felipe at synergy com
I am a C, modern C++, MFC, ODBC, Windows Services, MAPI developer
from synergy, and Computer Science student from State
University of Campinas(UNICAMP).
To know more about :
Unicamp: http://www.ic.unicamp.br
Synergy: http://www.synergy.com.br
current work: http://www.mintercept.com
| |
| Tom Widmer 2005-03-15, 4:02 pm |
| Felipe Magno de Almeida wrote:
> Tom Widmer wrote:
>
>
> What kind of obscure bugs? is there any page saying anything about it?
Well, there are a few arguable bugs (i.e. it doesn't work the way I
think it should, but the standard is ambiguous). I found an outright bug
where I got an access violation if memory was exhausted when
constructing an ostream object (which is hardly likely to happen).
Otherwise, search this group on google - there may be a few confirmed
bugs that have been reported. I don't know of any webpage listing them
though.
Tom
| |
|
|
| Carl Daniel [VC++ MVP] 2005-03-15, 4:02 pm |
| "Carl Daniel [VC++ MVP]" <cpdaniel_remove_this_and_nospam@mvps.org.nospam>
wrote in message > bug in std::next_permutation() (patch included in the
message)
> http://groups-beta.google.com/group...ed7b9fc25819cc6
sorry - that bug is in prev_permutation, not next.
-cd
| |
| schapparam 2005-03-16, 5:04 pm |
| quote:
Originally posted by Carl Daniel [VC++ MVP]
schapparam wrote:
> We found issues with MS STL version 6.0 with STL container classes.
> Want to know if they are resolved now in VC .NET 2003?
Such as?
Have you looked at the patches for VC6 (and VC5) STL at
http://www.dinkumware.com/vc_fixes.html
?
-cd
WE looked at those but we were not allowed to apply these "outside" patches so we went with RogueWave's STL as we anyway use RogueWave libraries for other things. Now that we are moving to VC .NET, trying to determine whethere these bugs (dincumware fixes) have gone into Vc .NET or now. Also we had an issue with std::string in MS STL...changing to RWCString solved the issue. It caused a heap corruption when we tried to allocate and deallocate in a loop. | |
| Carl Daniel [VC++ MVP] 2005-03-17, 4:00 am |
| schapparam wrote:
> Carl Daniel [VC++ MVP] wrote:
>
> WE looked at those but we were not allowed to apply these "outside"
> patches so we went with RogueWave's STL as we anyway use RogueWave
> libraries for other things. Now that we are moving to VC .NET, trying
> to determine whethere these bugs (dincumware fixes) have gone into Vc
> NET or now. Also we had an issue with std::string in MS STL...changing
> to RWCString solved the issue. It caused a heap corruption when we
> tried to allocate and deallocate in a loop.
I'd suggest that you need to do testing on your own to determine if VC++ 7.1
and it's associated version of STL meets your requirements. If you can post
specific test cases (complete code!) that failed on VC6, I'm sure someone
can tell you if they pass on 7.1.
-cd
| |
|
| "Carl Daniel [VC++ MVP]" wrote in message
> schapparam wrote:
>
> Such as?
>
> Have you looked at the patches for VC6 (and VC5) STL at
>
> http://www.dinkumware.com/vc_fixes.html
I wonder why they didn't include the fixes (they are from 2002 and before)
into the MS Service Pack(s), or why they don't make the changed files available.
Instead one has to apply the fixes manually into the files...
| |
| Stephen Howe 2005-04-12, 8:59 am |
| > I wonder why they didn't include the fixes (they are from 2002 and before)
> into the MS Service Pack(s)...
Because unfortunately Dinkumware were locked in a lawsuit that has happily
been resolved.
I am sure you can use Google to find out details if you want. During that
time, Microsoft did not apply any changes to the standard C++ library in VC6
Service Packs.
Stephen Howe
| |
| Igor Tandetnik 2005-04-12, 4:01 pm |
| "Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom> wrote in message
news:udENa80PFHA.3336@TK2MSFTNGP09.phx.gbl
>
> Because unfortunately Dinkumware were locked in a lawsuit that has
> happily been resolved.
> I am sure you can use Google to find out details if you want. During
> that time, Microsoft did not apply any changes to the standard C++
> library in VC6 Service Packs.
Somewhat disturbing is the fact that these changes (nor other bugfixes,
say for known and documented ATL issues) made it into VC6 SP6, which was
released fairly recently.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
|
|
|
|
|