Hi,
On Sep 15, 2016, at 10:16 PM, Nicolai Hess <nicolaihess@gmail.com> wrote:
2016-09-15 8:12 GMT+02:00 Tudor Girba <tudor@tudorgirba.com>: Hi,
On Sep 15, 2016, at 7:50 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
We can change it back and maybe add support for the reformatter to not convert it to the literal array #(3 #+ 4) .
I do not know in fact this is why I asked :) Now may be my idea to use pragma to get something like pythondoctest is a bad idea but I really want to have literal programming. What do you think?
I like the idea to show examples/tests close to code, but pragmas are not really good...
If we have ' ' then it would be good that the syntax higlighter works with a special mode inside the ' '
it is just a string. How do you know that it contains code?
Would you highlight all string in all code as if it contained code? Or would you add this just for Pragmas? But even there, strings are string, not code.
I think we can conclude that pragmas are not a good solution to the problem, as they are far too limited to express code.
I second that.
Furthermore, typical examples require more than one liners, and these should be factored out separately.
I really like the one liners that you can find im some method comments, like in Color class>>#wheel: if you are new to pharo and start exploring the system, it makes fun to see these little one lines and just execute it. (even if they aren't onelines like in some method in class Form).
I like one liners, too. But, should a documentation mechanism be confined to only work with small examples? Cheers, Doru
Cheers, Doru
Marcus
-- www.tudorgirba.com www.feenk.com
"Every thing should have the right to be different."
-- www.tudorgirba.com www.feenk.com "Reasonable is what we are accustomed with."