Re: Why does Ada.Iterator_Interfaces specify Next as a function rather than a procedure?

["Randy Brukardt" <randy@rrsoftware.com>]

<briot.emmanuel@gmail.com> wrote in message 
news:806ff091-efd2-4625-afec-c7a6dc7886a8@googlegroups.com...
>In my experience, a simpler approach is to use GNAT's Iterable aspect, 
>which
>is way simpler and more logical (really just a thin layer about the usual
>Cursor/Has_Element/Next/... operations).

If he's trying to create portable Ada code, that's hardly an option. Perhaps 
Ada 202x will include an easier solution to the problem.

I tend to agree that the use of interfaces here was a mistake; we ended up 
needing a bunch of aspects to make the solution usable, and at that point we 
should have just abandoned the interfaces and just used aspects. (This is 
one of my reasons for saying that interfaces themselves are pointless.) In 
any case, though, portable Ada code is stuck with them.

                                     Randy.