** Changed in: zorba
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/867262
Title:
Ext func arg item seq can not be consumed 2 times
Status in Zorba
** Changed in: zorba
Status: Fix Released => Fix Committed
** Changed in: zorba
Milestone: None => 2.1
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/867262
Title:
Ext func arg item
** Changed in: zorba
Status: New => Fix Released
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/867262
Title:
Ext func arg item seq can not be consumed 2 times
Status in Zorba - The XQue
What about this bug? Is it done?
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/867262
Title:
Ext func arg item seq can not be consumed 2 times
Status in Zorba - The XQuery Processor:
New
Bu
I think it's fine to restrict the API to only allow one iterator at a time. If
the user has a use case
that requires two active iterators at a time, he should think about his use
case and eventually
materialize in his code.
I'm going to approve the merge proposal.
--
You received this bug noti
Gabriel, would it be ok with your use case if instead of calling
getIterator() a second time, you reused the same iterator? Basically,
the code would look something like this:
Item item;
Iterator_t iter = args[0] ->getIterator( );
iter->open();
iter->next(item);
iter->close();
// iter = args[0]
6 matches
Mail list logo
