- From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
- Date: Mon, 18 May 2009 16:10:01 +0200
Using entities in XSL to share code was my mistake once too; it is similar to using data members not wrapped in properties in data types. XSL itself provides a better structured approach for code reuse. Being able to use localized programming language constructs is at the same time trivial (replace this with that), expensive (you have to translate the documentation) and not that useful (you freeze the language and cut the programmers off from the recent developments in the language). Languages tend to use English keywords regardless of the culture of their designer because: 1. no matter how deep you go, there is always a place where you have to switch to English in order to refer to some precedent technology, 2. the English words/roots used in the language design often have a slightly different meaning from the English source, 3. they are sufficiently few to be learned easily; it may be harder to grasp what they actually mean in the particular context. (Toy languages for children make an exception, of course; however, even children tend to mock them nowadays.) Best regards, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090518/ae5eca97/attachment.htm>
Received on Monday, 18 May 2009 07:10:01 UTC