[Versa] Versa Extension Bug (or lack of support) added to SF

[Chimezie Ogbuji]

http://sourceforge.net/tracker/?func=detail&atid=428292&aid=1263032&group_id=39954

I've added an issue to the SF bug tracker outlining my issue with
defining Versa Extension functions, so it's on the radar.  Summarized
below:

Versa has *no* mechanism for extending it's function library
Currently, whenever I need to define a new extension
function for Versa (which is very often for me), I end
up having to overwrite
Ft/Rdf/Parsers/Versa/__init__.py in order update
g_extFunctions = {}
with the extension functions. For example:

g_extFunctions = {}

from VersaFuXiExtensions import FUNCTIONS
from Ft.Share.ExtensionModules.VersaExtensions import
FUNCTIONS as CIDRVersaFunctions
g_extFunctions.update(CIDRVersaFunctions)
g_extFunctions.update(FUNCTIONS)

This is bad because I can't have seperate software
installations add their own extensions w/out manually
editing that file to account for both *and* if that
file ever changes in the CVS tree those changes would
be overwritten by the installation process. Given that
we have a precedent with our XPath/XSLT implementations
I would think it wouldn't be hard to have a bare bones
mechanism for registering extension functions - or
perhaps the problem is with the specification which
isn't very clear on how this should work.

Chimezie