This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hey y'all. Here's an idea for the way tr1::array should be tested. This is not complete, but I thought I'd post it anyway. As an experiment, I thought I'd try to do a more complete job with this container than with some of the existing (standard) containers, and then take the results of that experience and apply it to the standard containers. So, some of this is thinking outloud.... So. Does this organization look sane to people? Could the names be improved? Do you think it makes sense to do things like typedef, instantiation, and inheritance checks as part of the "requirements" directory? Some of the bits listed in the container requirements tables actually can be tested in things like the iterator directory. The goal, of course, is to actually check container requirements, at some level, as well. That work is in-progress. I would like to do a complete job for tr1::array, and then generalize to all containers, and at that point extract common code to the testsuite_*.h include files. I'm unsure as to if I should try to do a fully complete job on tr1::array, and then check this in, or check it in incrementally. Thoughts? tested x86/linux
Attachment:
p.20041020
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |