2016-09-15 17:09 GMT-03:00 Tudor Girba <tu...@tudorgirba.com>: > However, one thing to keep in mind is that one reason why these solutions > exist is because they assume no UI environment. Thus, the only thing they > have is text and the solution is built around it. > > In Pharo, we can think of concatenating information in the environment. If we > have a casual connection between examples and the code they exemplify, the > interface can provide all this information at the same time. The advantage > here is that the syntax remains simple.
+1 I wouldn't like that syntax, nor PharoDoc (a la JavaDoc), nor anything "polluting" the code that way. The comment or examples can be attributes of the method itself, just like the class comment are today. Regards! Esteban A. Maringolo
