cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject Re: proposed pipeline-hints syntax
Date Mon, 16 Sep 2002 17:00:10 GMT
Michael Melhem wrote:

>Hi Sylvain,
>
>I have implemeneted the pipeline-hints syntax as follows:
>
>A hints attribute has one or more comma separated hints
>hints-attr :: hint [ ',' hint ]*
>A hint is a name and an optional (string) value
>If there is no value, it is considered as boolean string "true"
>hint :: literal [ '=' litteral ]
>literal :: <a character string>
>
>Plus the normal sitemap variable resolving.
>
>*However*, I did not implement the following rule :
>Any  ',' and '=' within a literal must be escaped with '\'
>
>This means that ',' and '=' are not permitted with any "literal"
>
>Was there a specific reason you wanted the above (escape) behavior?
>Does it make sense to have comma or equals within a literal?
>Implementing the above makes spliting on "comma" and "equals"
>less trivial so I was wondering if it was worth the extra effort
>implementing it (if there was no specific need for it)?
>
>Let me know what you think! :-)
>

Well, let's do it step by step. Don't handle escaping for now, and we 
will add it when someone claims he wants commas in values !

For '=', I think we will never need to escape it as I don't see why 
people would have hint names containing a ',' or a '='...

Sylvain

-- 
Sylvain Wallez
  Anyware Technologies                  Apache Cocoon
  http://www.anyware-tech.com           mailto:sylvain@apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message