new version of array<>

From: Nicolai Josuttis (nico_at_[hidden])
Date: 2000-07-31 16:43:19

Attached is the new version of array<> as complete file tree
(see array_all.tgz).
It has the modifications mentioned in the CHANGELOG attachment,
which are all major wishes after the formal review
(thanks for all feedback).
Of course, it's still not perfect.
But it should be good enough to put it on the web.

Same urgent questions I have:
- How to implement a template assignement operator that
  makes sure that the same number of elements are used?
- Does anybody know whether using "{...}" instead of
  "{ { ... } }" for initialization is valid code???

NOTE: I don't have time to rerae boost messages anymore.
Thus, please send any comment as a copy to me!!!
Also, I might have ignored remarks in recent mails.
I'll try to catch up, but in case there was something important
for me and anybody has a summary for me, just feel free
to send it to me.
Thanks.

Please excuse the delay. I have plenty things to do.

Best
 Nico

-- 
Nicolai M. Josuttis          	http://www.josuttis.de/
Solutions in Time        	mailto:solutions_at_[hidden]

- include boost/config.hpp instead of re-doing std::size_t workaround
- making rangecheck() const
- making size(), empty(), max_size() static
- empty() simply returns false
- static_size to use size at compile time
- data() for direct access to elements
  (note, I only allowd read-only access)
- op=, op<, swap() implemented with standard algorithms
- minor fixes of text and comments
- new example and test case array5.cpp

OPEN:
- template assignment
- assign()
- more boost L&F on web pages (cross links, boost gif, ...)
- Jens Maurer <Jens.Maurer_at_[hidden]>:
    Do we want the "using std::swap;" trick so that Koenig lookup finds
    more global element swap() functions?
  What's that????
- Could "{...}" be used instead of "{ { ... } }" ???

DENIED:
- removing endl overhead in examples
  (in favor of readability)
- PRINT_ELEMENTS() still ALL_CAPS (again for readability,
  I could turn it into a macro, though :-)