Re: about DoublyLinkedList

"Hugo Santos" <[email protected]> wrote:
>   This iterator approach allows easily for items to be removed since
> it always keeps an extra pointer for the next item; but i find this
> use case to be a particular case and not the general case. I'll 
> gladly
> follow the current convention though.

You can use a const iterator in that case - same with the STL.

>   Personally, my point for a different approach is that the STL-like
> interface better maps concepts such as "First" versus the Java
> approach where Iterators are mostly Visitor objects. I think concepts
> result in more understandable code, but i guess that's a personal
> opinion.  Also, the STL isn't going anywhere and having an interface
> which is similar to it helps new developers. :-)

I disagree - the consistent feel of an API (such as the Be API) is more 
important than to copy existing APIs. The STL is available anyway (not 
in the kernel, because of exceptions, though).
I never liked the STL container API while I immediately liked the Java 
container API, for example :-)

Bye,
   Axel.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV