Re: Is CArray best for this...
- From: Norbert Unterberg <nunterberg@xxxxxxxxxxxxxxxxx>
- Date: Thu, 17 Jan 2008 13:10:26 +0100
David Wilkinson schrieb:
[...]
It is rather that, IMHO, CArray was poorly designed at the beginning compared to std::vector:
1. Confusing double template argument
2. Confusing helper functions
3. Confusing duplication in operator [], GetAt() and ElementAt()
4. No copy constructor or assignment operator
5. Non-portable
You forgot one:
6. It scales very bad when used with large amount of data.
Norbert
.
- Follow-Ups:
- Re: Is CArray best for this...
- From: David Ching
- Re: Is CArray best for this...
- References:
- Is CArray best for this...
- From: GT
- Re: Is CArray best for this...
- From: AliR \(VC++ MVP\)
- Re: Is CArray best for this...
- From: GT
- Re: Is CArray best for this...
- From: AliR \(VC++ MVP\)
- Re: Is CArray best for this...
- From: GT
- Re: Is CArray best for this...
- From: AliR \(VC++ MVP\)
- Re: Is CArray best for this...
- From: AliR \(VC++ MVP\)
- Re: Is CArray best for this...
- From: GT
- Re: Is CArray best for this...
- From: David Wilkinson
- Is CArray best for this...
- Prev by Date: Re: Using a callback function name as an argument in a function
- Next by Date: Re: Whither GUI conventions?
- Previous by thread: Re: Is CArray best for this...
- Next by thread: Re: Is CArray best for this...
- Index(es):
Loading