small bug in Basex
Monday, 20 January 2014 · 2 messages
RS
Rob Stapper20 Jan 2014 10:00 #
Hi,
While studying Leo's "Higher-Order XQuery Modules" I encountered a small bug in Basex. Probably a wrongly timed initialization of an internal locationpath-variable.
If Basex starts with an editor-window active that contains a query with a doc-statement that contains a relative path, than when directly running this query triggers an error, see attachement: basex-error.txt.
Leo's dijkstra-query also suffers from it.
Regards,
Rob Stapper
PS. Leo's modules made me understand programming functional data structures in Basex. Thanx for that.
---
Dit e-mailbericht bevat geen virussen en malware omdat avast! Antivirus-bescherming actief is. http://www.avast.com
CG
Christian Grün20 Jan 2014 11:15 #
Hi Rob,
Quoted text · Rob Stapper · 1 line
> If Basex starts with an editor-window active that contains a query with a doc-statement that contains a relative path, than when directly running this query triggers an error, see attachement: basex-error.txt.
I think I need some more information. I have opened a new BaseX GUI instance, I’ve copied the query..
doc('../resources/dictionary.xml')..to the editor panel, and when executing it, I get a proper error message (FODC0002).
What’s the easiest way to reproduce the bug?
Thanks,
Christian
Quoted text · Rob Stapper · 28 lines
> > Leo’s dijkstra-query also suffers from it. > > > > Regards, > > > > Rob Stapper > > > > PS. Leo’s modules made me understand programming functional data structures in Basex. Thanx for that. > > > > ________________________________ > > Dit e-mailbericht bevat geen virussen en malware omdat avast! Antivirus 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.7. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery