Re: Yet another idea

["Alexey Parshin" <alexeyp@gmail.com>]

C++ iterators is something I'm trying to hide.. If we can't find a
good way to present embedded loops, then the whole idea is useless.

I'm trying to imagine how we can use it.. Something like:

Topics.forEach(
    "  topic template 1 here ",
    SubTopics.forEach( " subtopic template here "),
   "  topic template 2 here "
);

It isn't a problem to implement variable number of parameters. It's a
problem then we have too much C++ again :(

2008/7/1 Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com>:
> Alexey Parshin wrote:
>>
>> Topic is a UMO, with a name, type, and title. Any other fields are not
>> essintial for this example. topics is ether std::vector<CUMO> as in
>> current approach, or CRecordSet<CUmo> as I propose to do it.
>> In that case, CRecordSet class should implement forEach() method.
>>
>> There is an interesting flaw that my current idea doesn't cover yet.
>> forEach() works ideally for one-level loops, such as a recordset
>> converted to some html. However, it doesn't yet provide the method for
>> embedded loops.
>>
>
> Aha. Now I understand somewhat better what you meant, and like it far more
> :)
> Re: embedded loops, we can either solve it by making a complex ways of
> defining which substitutions cause calls to sub-objects forEach(), or just
> by going
> back to good old C++ iterators, in those rare cases that need it.
>
>



-- 
Alexey Parshin,
http://www.sptk.net