+1 Graham
Torsten Bergmann wrote:
Hi Tudor, we all already had exchanged on this topic in discussions on this list back a year ago or even before and as we have seen there were different arguments and different point of views. Actions to make Pharo more known are always appreciated and as you made more progress on the idea/tools side for sure you can demonstrate better what can be done with this approach. But does it mean all the other arguments are now invalid because of this? I don't think so. Anything described/demonstrated in this approach can perfectly be done without changing the meaning of the "example" pragma and by using an own pragma to mark methods following that idea. Trying to hijack "example" pragma again as it is your preferred pragma name does not help because this is like enforcing your own point of view on the topic to people like me following the existing "example" usage. Currently<example> and its usage is very generous and not so restrictive what kind of example the method contains or what return value it may provide. Also counting the current usage in the default image does not tell you anything as it leaves out all external projects. Similar to Ben I personally have not changed my point of view. I agree with him in using an own and more specific pragma like -<sample> -<sampleInstance> -<exemplar> better depicting the meaning of returning an sample/sample instance/exemplar of an instance of the class. I would be fine with using just "sample" as well as "Sample driven development". There is no need to change the meaning of the existing pragma<example> which is more general and can be any kind of example like: - example of usage - a simple example script - sample instance - example of an algorithm - example on how to use several classes together - ... For<example> it is not necessary to return exactly once instance of the class where the pragma is used in. Thx T.
<<attachment: graham.vcf>>
