| Author |
 Topic  |
|
|
Alexo
Ketchup Master
Canada
81 Posts |
 Posted - Feb 25 2009 : 2:25:24 PM
|
VS2005+SP2
VAX 1715
The suggested member list is incorrect.
I a real case (which, unfortunately, I cannot post), VAX gets confused after the first operator and presents a member list from a completely unrelated structure. The differences from the test-case:
1. The structures have some more data members and methods
2. STLPort is used instead of native STL.
|
Edited by - Alexo on Feb 25 2009 2:26:36 PM |
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Feb 26 2009 : 6:12:15 PM
|
Have you tried to reproduce the problem in a simple case like this, also with stlport?
stlport has a different codebase, so if I put this bug report with STL, it may not solve your problem.
I'm setting up stlport here to do some tests. |
Edited by - accord on Feb 26 2009 6:20:41 PM |
 |
|
|
Alexo
Ketchup Master
Canada
81 Posts |
Posted - Feb 27 2009 : 10:40:46 AM
|
Hi accord,
quote:
Originally posted by accord
Have you tried to reproduce the problem in a simple case like this, also with stlport?
The subset of the project I'm working on has 20 projects in the solution comprising over 2K of files totalling about 1M LOC. Extracting small but meaningful test cases that reproduce the behaviour is not always trivial.
While I am happy to assist, there is only so much time that I can spend on this activity without a reprimand from my boss (at work) or my other boss (at home).
I was under the impression that Whole Tomato has a QA team.
However, here's a suggestion to make testing with and without STLPort easier:
1. Create a new property sheet (call it stlport.vsprops or whatever)
2. In "Common Properties | C/C++ | General" of the property sheet, set "Aditional Include Directories" to:
C:\\work\\root\\stlport;"$(VcInstallDir)include";"$(VcInstallDir)PlatformSdk\\include"
(but see note below!)
Note: This works for native C++ without ATL/MFC. The full list should probably be taken from the global list in:
"Tools | Options | Projects and Solutions | VC++ Directories | Include files"
3. In "Common Properties | C/C++ | Preprocessor" of the property sheet, set "Ignore Standard Include Path" to: Yes.
4. In the configuration properties of the project you want to test, go to "Configuration Properties | General"
and add the path to your new propery sheet into the "Inherited Project Property Sheets" field.
Now, testing with STLPort or with the native STL is only a question of adding or removing the property sheet as described in step #4 -- for every project you wish to test (probably followed by a global reparse to keep VAX synchronized).
As a general aside, I find the property sheet mechanism very helpful, particularly when combined with the $(Inherit) and the $(Noinherit) macros for additional fine-tuning.
Best regards,
Alex.
|
Edited by - Alexo on Feb 27 2009 10:48:53 AM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19177 Posts |
Posted - Mar 03 2009 : 11:24:22 AM
|
We do have a QA team, but sometimes it is hard to know where to start with bug reports without more details.
It turns out that STLPort is not required, I can reproduce this problem using the IDE's standard STL:
case=24631
Thank you for the very clear description. |
zen is the art of being at one with the two'ness |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - May 12 2011 : 12:48:52 AM
|
| case=24631 is fixed in build 1848 |
Whole Tomato Software, Inc. |
|
|
|
Alexo
Ketchup Master
Canada
81 Posts |
Posted - May 12 2011 : 12:59:26 AM
|
| Wow, that was quick! |
|
|
| |
Topic |
|
bug: nested containers
