On Fri, Mar 21, 2014 at 5:06 PM, Andrew Welch
<andrew(_dot_)j(_dot_)welch(_at_)gmail(_dot_)com> wrote:
Correct me if I'm wrong but couldn't you say the same thing over each
and every application of xsl:attribute-set
No - how would it be possible to cause a similar exception using
attribute-sets? An example of what you mean would help here.
Now that I look at the syntax it may not be.
It's an anti-pattern.
Yes I'm sure there's another way of achieving the same thing but I'd
rather be anti-pattern than anti-declarative.
? It's not "anti-declarative" (actually I can't say that it isn't
because I don't know what that is) It's just a common mistake.
You cannot say it's a mistake.
It's a trade-off and when considering which evil you elect for you do
a little risk analysis.
What is the likelihood of events that would lead to an exception
occurring, how calamitous would it be if it did occur, how hard and
costly and time consuming is it to implement and roll out the fix.
Also if you are am not doing big object oriented software engineering
you don't have to live by that bible.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--