Altova Mailing List Archives

Re: [xml-dev] Refreshed genx.h, plus some plans

From: Rich Salz <rsalz@---------.--->
To: Karl Waclawek <karl@--------.--->
Date: 1/24/2004 10:52:00 PM
> > int genxDeclareNamespace(genxWriter w, utf8Byte * uri, utf8Byte *
> > prefix);
> >
> > if prefix == NULL then genx will generate one.  prefix == "" is not
> > allowed.
> What about default namespaces?

I'd do this.  Add this to your header:
        extern char genxDEFAULT_NAMESPACE[1];
and this to your implementation:
        char genxDEFAULT_NAMESPACE[1] = { 0 };
and then users do
        int genxDeclareNamespace(w, "urn:foo:bar", genxDEFAULT_NAMESPACE);
And then you do a pointer comparison to see if users passed in default.

BTW, the API doesn't have const-correctness yet.

> Maybe NULL should mean "default namespace", and you add a second function:
>   int genxDeclareAutoNamespace(genxWriter w, utf8Byte * uri);
> which auto-generates a prefix.

Again, a new "pointer constant" will remove the need for a new function.


Rich Salz                  Chief Security Architect
DataPower Technology
XS40 XML Security Gateway
XML Security Overview


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.