Property name syntax?

Yes, that a question... In trying to figure out why I was
having 
problems using a property named
"<doxygen:processor>" I ran into this:

===
# We don't add default for elements with ":"
inside. This catches:
# 1. Conditional properties --- we don't want
<variant>debug:<define>DEBUG
#    to be takes as specified value for <variant>
# 2. Free properties with ":" in values. We don't
care, since free 
properties
#    don't have defaults.
===

Hence my question. Is there some description of what a
property name 
syntax should be? Especially what kinds of chars we should
not use in a 
property name?


-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software
.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

on Thu Apr 05 2007, Rene Rivera
<grafikrobot-AT-gmail.com> wrote:

> Yes, that a question... In trying to figure out why I
was having 
> problems using a property named
"<doxygen:processor>" I ran into this:
>
> ===
> # We don't add default for elements with ":"
inside. This catches:
> # 1. Conditional properties --- we don't want
<variant>debug:<define>DEBUG
> #    to be takes as specified value for
<variant>
> # 2. Free properties with ":" in values. We
don't care, since free 
> properties
> #    don't have defaults.
> ===
>
> Hence my question. Is there some description of what a
property name 
> syntax should be? Especially what kinds of chars we
should not use in a 
> property name?

I can't answer that, but I say that it's safe to use '.'
instead of
':'

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

Don't Miss BoostCon 2007! ==> http://www.boostcon.com

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build