From: Loren C. <lor...@gm...> - 2012-09-01 16:19:40
|
Confirmed! I will test with the RestXQ enhancements later this evening US Central time. On Sep 1, 2012, at 10:44 AM, Adam Retter <ad...@ex...> wrote: > Thanks guys, this issue is now fixed as revision 17041. > > On 31 August 2012 20:54, Adam Retter <ad...@ex...> wrote: >> On 31 August 2012 20:36, Wolfgang Meier <wol...@ex...> wrote: >>>> "[Definition: A module M1 directly depends on another module M2 >>>> (different from M1) if a variable or function declared in M1 depends >>>> on a variable or function declared in M2. >>> >>> This refers to dependencies between functions or variables, which may not recursively depend on each other. The following section is pretty clear though: >>> >>> "J.4 Cycles >>> >>> It is not an error to have a cycle in the import graph, either at the level of module URIs or at the level of location URIs. The only rules concerning cycles affect the relationships between functions and variables defined in different modules." >>> >>> http://www.w3.org/TR/xquery/#id-module-handling-cycles >>> >>> Cyclic imports are pretty normal in well-written code. They were a problem back in the old C days, but modern compilers can handle this. >>> >>> Wolfgang >> >> Okie dokie, I should be able to fix the recursive issue shortly... >> >> >> -- >> Adam Retter >> >> eXist Developer >> { United Kingdom } >> ad...@ex... >> irc://irc.freenode.net/existdb > > > > -- > Adam Retter > > eXist Developer > { United Kingdom } > ad...@ex... > irc://irc.freenode.net/existdb |