a) or b)

[Tobias Oetiker <nospam@thanx>]

Today you sent me mail regarding [wml] Re: [wml] Re: [wml] Re: WML 2.0.1:

*> I know this doesn't answer your question, but I always found this syntax
*> awful. It just doesn't fit with my understanding to have all the
*> expanded stuff between the <>'s. I think nesting of <> is to be avoided
*> where possible.
*> 
*> As someone else suggested, I'd like a syntax like this:
*> 
*> | <ifeq 0 0>
*> |      then-case
*> |   <else> (optional)
*> |      else-case
*> | </ifeq>
*> 
*> Not much more to type, but nontheless far more clear. I mean, if we're
*> breaking compability anyway, why not do it right ?

Sec,

The problem is not <ifeq in particular ... this thing with having
<else> is certainly a good idea for this problem, but we have to
find a general sollution to the tag nesting problem and the fact
that we have a mixed bag of known and unknown tags ... completely
aside of the <ifeq problem ...

Regarding Denis question, I think solution b) is a good. Especially
if you think about the case where you think about first working
with normal html tags and then gradually replacing them with WML
defined tags. In case a) this would mean to rewrite all the pages
where you have been using the non defined tag because its parsing
is suddenly changed around ... 

cheers
tobi

*> CU,
*>     Sec
*> 

-- 
 ______    __   _
/_  __/_  / /  (_) Oetiker, Timelord & SysMgr @ EE-Dept ETH-Zurich
 / // _ \/ _ \/ / TEL: +41(0)1-6325286  FAX:...1517  ICQ: 10419518 
/_/ \.__/_.__/_/ oetiker@ee.ethz.ch http://ee-staff.ethz.ch/~oetiker

______________________________________________________________________
Website META Language (WML)                www.engelschall.com/sw/wml/
Official Support Mailing List                   sw-wml@engelschall.com
Automated List Manager                       majordomo@engelschall.com