From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,f2690a5e963b61b6
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!feed.news.tiscali.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.arcor.de!news.arcor.de!not-for-mail
Date: Wed, 06 Jul 2005 12:45:10 +0200
From: Georg Bauhaus <bauhaus@futureapps.de>
Organization: future apps GmbH
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.7.8) Gecko/20050513 Debian/1.7.8-1
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: GCC 4.0 Ada.Containers Cursor danger.
References: <1120474891.635131.216700@g44g2000cwa.googlegroups.com>
 <42C98672.3020705@arcor.de> <dag75j$1ccj$1@pandora.alkar.net>
In-Reply-To: <dag75j$1ccj$1@pandora.alkar.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <42cbb631$0$10808$9b4e6d93@newsread4.arcor-online.net>
NNTP-Posting-Date: 06 Jul 2005 12:45:05 MEST
NNTP-Posting-Host: 0c07c7cb.newsread4.arcor-online.net
X-Trace: 
 DXC=A>[;:`5oASA4mA>;52^R7K:ejgIfPPldDjW\KbG]kaMHliQbn6H@_EIni6]Q<aYHUJUUng9_FXZ=C>:=P9Ihe`BH@Z?dZ]MOidE
X-Complaints-To: abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:11892
Date: 2005-07-06T12:45:05+02:00
List-Id: <comp.lang.ada>

Maxim Reznik wrote:

> I agree with Dmitry such behavior of Cursors is very dangerous
> and should be avoided.

That's what Matthew has said: You don't have to use
Cursors with maps. The library is generous enough to
provide Cursors, should you need them for some reason.

> If container knows all his cursors it can do it easy.

The knowledge + checking results in performance loss.

> There are a very few cursors per container in typical program,
> so it is not big work.

Care to give some data? It is difficult to argue about
hot air.

> And safety here is much important then performacne.

Sometimes performance is a *requirement* for achieving
safety, there is no trade-off between speed and checking
access then. E.g. response time must be within some limit,
therefore the container algorithm must work within
O(the-function-here).


Georg