From: Dave F. <dav...@gm...> - 2012-12-03 15:27:21
|
Ah, got it. I'm still processing my first cup of coffee this morning. This worked for all function calls except for the following error I get. I've tried the math and math-ext namespaces, but the power() function doesn't exist in either Function math-ext:power() is not defined in module namespace: http://exist-db.org/xquery/math On Mon, Dec 3, 2012 at 9:23 AM, Dannes Wessels <da...@ex...> wrote: > it should read math-ext:abs() ; > > note that the w3c/math namespace does not contain the abs() function > ...... that is why I retained the math-ext: namespace :-) > > anyway, i'll bring the original functions back again, mark them > deprecated, to have them removed in 2.1/2.2/.... > > cheers > > Dannes > > > On Mon, Dec 3, 2012 at 4:19 PM, Dave Finton <dav...@gm...> wrote: > >> Is there by chance a workaround to this error I am getting? I tried using >> "mathext" as the namespace as suggested previously, but the nature of the >> error did not change at all: >> >> Function math:abs() is not defined in module namespace: >> http://www.w3.org/2005/xpath-functions/math >> >> Other math functions I have dependencies on are math:ceil, math:floor, >> and math:power. >> >> I tried referring to the documentation but I'm also having difficulties >> getting the dashboard to work properly today. ;) >> >> >> On Sun, Dec 2, 2012 at 3:59 PM, Adam Retter <ad...@ex...> wrote: >> >>> >>> Aahhh, right, I did not think about the deprecation possibility. Hmmmm >>>> there is one serious issue however, the default 'prefix' "math" is now used >>>> by the 'official' namespace, that would cause a problem anyway? I >>>> relabelled it to "math-ext". >>>> >>> >>> You dont need to change the prefix. The prefix is opaque, its the >>> namespace that matters. That said it doesnt matter if you change the prefix >>> because it is opaque. >>> >>> >>>> >>>> hmmmm I deleted the double functions already, well I can revert it if >>>> we want to. >>>> >>> >>> I think we must. >>> >>> >>>> Can we think of a smart design where the old extension uses code from >>>> the new function library? The ultimate goal is not to have double code (I'd >>>> rather avoid that, politely said) >>>> >>> >>> Sure, bring the math module into the core code-base rather than as >>> external and then abstract the core code into business logic classes and >>> call from both function wrappers. Or only move the now W3C common code into >>> the core, abstract it still and then have the math module call it. >>> >>> >>>> >>>> cheers >>>> >>> >>> Cheers :-p >>> >>>> >>>> Dannes >>>> >>>> eXist-db Native XML Database >>>> http://www.exist-db.org >>>> >>>> >>> >>> >>> -- >>> Adam Retter >>> >>> eXist Developer >>> { United Kingdom } >>> ad...@ex... >>> irc://irc.freenode.net/existdb >>> >>> >>> ------------------------------------------------------------------------------ >>> Keep yourself connected to Go Parallel: >>> DESIGN Expert tips on starting your parallel project right. >>> http://goparallel.sourceforge.net/ >>> _______________________________________________ >>> Exist-development mailing list >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-development >>> >>> >> >> >> -- >> David Finton >> > > > > -- > eXist-db Native XML Database - http://exist-db.org > Join us on linked-in: http://www.linkedin.com/groups?gid=35624 > -- David Finton |