Hi, Nobody answered Andreas proposition that I find really interesting. No debate about the number of methods using this pragma or the other one: we do not care! What is important is: "does the pragma name says me what I can expect from this method?" If you look at the number of messages in this thread, I would say no. So why not choosing different names for different things? <exampleCode> and <exampleInstance> Le 25 mars 2015 à 18:23, Andreas Wacknitz a écrit :
For me one really important thing is: get the names right. 4.0 will be released soon. What is being introduced now will stay for a while.
You discussion makes it clear to me that <example> is misleading and thus not an optimal name (for both usages). So it would be better to choose something more intention revealing like <exampleCode> and <exampleInstance>. This also makes room for more example ideas in the future.
+1 Christophe.