For the very same reason I prohibit my colleagues from having defaulted attributes in an XML DTD - it becomes uninterpretable in absence of the DTD.
Generally speaking, implicit information declared elsewhere obfuscates (because it's present even when omitted). Attila. ----- Original Message ----- From: "Hensley, Richard" <[EMAIL PROTECTED]> To: "'Velocity Developers List'" <[EMAIL PROTECTED]> Sent: 2001. november 26. 19:47 Subject: RE: #macro functionality > I agree with Jon, Paulo, and Daniel. > > It sounds very cool on the outset, however it reminds me of my C++ days > where default parameters caused so much confusion for programmers > unfamiliar with the code base that they needed classes before they could > even read the code. i.e. way to many magic tricks up the sleeve. > > -1 > > Please keep Velocity simple meaning easy to read a template, and easy to > predict what a template will do because all the information is present. > > Richard Hensley > mailto:[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > Confidentiality Notice: This e-mail message, including any attachments, > is for the sole use of the intended recipients and may contain > confidential and privileged information. Any unauthorized review, use, > disclosure or distribution is prohibited. If you are not the intended > recipient, please contact the sender by reply e-mail and destroy all > copies of the original message. > > -----Original Message----- > From: Paulo Gaspar [ mailto:[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> ] > > Without vote rights (just my 2 cents), I agree with Daniel and Jon. > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
