Macro Names

Hi all,

Is there any convention for macro names? If not, could I propose that macro names NOT have “white space” in them, as this is causing me some grief.

Cheers,

Ron.

+1

Let’s change the schema to use a token datatype for the macro/@name and
text/@macro attributes.On Feb 19, 2010 10:43 AM, “Jerome, Ron” <@Jerome_Ron> wrote:

Hi all,

Is there any convention for macro names? If not, could I propose that macro
names NOT have “white space” in them, as this is causing me some grief.

Cheers,

Ron.


Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev


xbiblio-devel mailing list
xbiblio-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

The schema already uses xsd:token. Would xsd:NMTOKEN be a suitable string
datatype (see http://books.xmlschemata.org/relaxng/ch19-77231.html)? It
seems that one doesn’t allow for spaces. Or should we stick to xsd:token and
apply a pattern?

Rintze

That seems right. Ron, that work for you?

Any objections?

Bruce

Sounds good to me.

Ron.________________________________________
From: Bruce D’Arcus [@Bruce_D_Arcus1]
Sent: Friday, February 19, 2010 11:13 AM
To: development discussion for xbiblio
Subject: Re: [xbiblio-devel] Macro Names

On Fri, Feb 19, 2010 at 11:08 AM, Rintze Zelle <@Rintze_Zelle> wrote:

The schema already uses xsd:token. Would xsd:NMTOKEN be a suitable string datatype (see xsd:NMTOKEN)?

That seems right. Ron, that work for you?

Any objections?

Bruce


Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.


xbiblio-devel mailing list
xbiblio-devel@lists.sourceforge.net

Made the change:

RintzeOn Fri, Feb 19, 2010 at 6:48 PM, Jerome, Ron <@Jerome_Ron>wrote: