bug or requirement
Sunday, 30 March 2014 · 2 messages
RS
Rob Stapper30 Mar 2014 10:18 #
Hi there,
In order to maintain consistency in my solution-patterns I seem to end up with the need for cyclicly chained/imported modules: module "A" imports module "B" which imports module "A".
Too bad that the "import module" command of Basex can't handle this type of structure. Now I can't access the functionality of "A" within module "B".
What are the chances in solving this issue?
Have a nice weekend,
Rob Stapper
---
Dit e-mailbericht bevat geen virussen en malware omdat avast! Antivirus-bescherming actief is. http://www.avast.com
CG
Christian Grün30 Mar 2014 10:21 #
Cycles in imports should be no problem, but I remember we fixed a bug related to that in the last weeks. Does the problem persist with the latest 8.0 snapshot? If yes, feel free to provide us with an example.
On Sun, Mar 30, 2014 at 10:18 AM, Rob Stapper <r.stapper at lijbrandt.nl>wrote:
Quoted text · Rob Stapper · 36 lines
> Hi there, > > > > In order to maintain consistency in my solution-patterns I seem to end up > with the need for cyclicly chained/imported modules: module "A" imports > module "B" which imports module "A". > > Too bad that the "import module" command of Basex can't handle this type > of structure. Now I can't access the functionality of "A" within module "B". > > > > What are the chances in solving this issue? > > > > Have a nice weekend, > > > > Rob Stapper > > > ------------------------------ > <http://www.avast.com/> > > Dit e-mailbericht bevat geen virussen en malware omdat avast! Antivirus<http://www.avast.com/>actief is. > > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > >
Written for BaseX 7.8. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery