Re: [Pharo-dev] About PythonDocTest for Pharo

I am sorry, but I want to said it: we have tests. Why tests are not for same purpose? (I would say they include it). As Tudor said: "they are way too disconnected from the code" And this needs to be solved. We already have nice feature in Nautilus: it shows "test icon" on covered

Re: [Pharo-dev] About PythonDocTest for Pharo

Ok this is your taste. My reality is different. Tests are far far away. I do not see them. They live in a different time zone. They are smart have a boring setup. I want documentation in front on my nose. No extra thinking no extra click Just right there. Stef Le 18/8/16 à 23:14, Denis

Re: [Pharo-dev] About PythonDocTest for Pharo

On Thu, Aug 18, 2016 at 11:28 PM, Denis Kudriashov wrote: > > 2016-08-18 13:32 GMT+02:00 stepharo : > >> withExtension: aString >> >> "Returns a new file reference with a different file extension" > > > Does this comment is really needed? > I only see

Re: [Pharo-dev] About PythonDocTest for Pharo

2016-08-18 13:32 GMT+02:00 stepharo : > withExtension: aString > > "Returns a new file reference with a different file extension" Does this comment is really needed? I only see extra word "different". And rest is same as method name. IMHO we should rename method to

Re: [Pharo-dev] About PythonDocTest for Pharo

Hi. 2016-08-18 9:34 GMT+02:00 stepharo : > withExtension: aString > > "Returns a new file reference with a different file extension" > > > value: '/tmp/file.log' asFileReference > > > ^ self withPath: (self path withExtension: aString) > > > So let me know what

Re: [Pharo-dev] About PythonDocTest for Pharo

As I already told you and the board, I will just leave if such a solution get pushed into Pharo. Hi, I like this problem very much. I think we are not leveraging the objects we have in the image. Tests can help, but they are way too disconnected from the code and they are not really useful

Re: [Pharo-dev] About PythonDocTest for Pharo

Hi, > On Aug 18, 2016, at 2:41 PM, stepharo wrote: > > Hi doru > > >> Hi, >> >> I like this problem very much. I think we are not leveraging the objects we >> have in the image. Tests can help, but they are way too disconnected from >> the code and they are not really

Re: [Pharo-dev] About PythonDocTest for Pharo

Hi doru Hi, I like this problem very much. I think we are not leveraging the objects we have in the image. Tests can help, but they are way too disconnected from the code and they are not really useful for detailed questions. I am also happy that you are considering the use of pragmas for

Re: [Pharo-dev] About PythonDocTest for Pharo

Hi, I like this problem very much. I think we are not leveraging the objects we have in the image. Tests can help, but they are way too disconnected from the code and they are not really useful for detailed questions. I am also happy that you are considering the use of pragmas for this

Re: [Pharo-dev] About PythonDocTest for Pharo

Tx serge - I think that we should agree on the pragma or way to express it. May be we can do the same as in Python and use a comment instead of a pragma. I prefer a pragma because we can query them easily. So any idea instead of withExtension: aString "Returns a new file

Re: [Pharo-dev] About PythonDocTest for Pharo

On Thu, Aug 18, 2016 at 9:34 AM, stepharo wrote: > Hi guys > > I'm fed up to get methods without comments and without little examples. In +1 ! We can setup a small group of people interested to build examples at ESUG. > FileSystem, I wrote most of the comments and I tried to

[Pharo-dev] About PythonDocTest for Pharo

Hi guys I'm fed up to get methods without comments and without little examples. In FileSystem, I wrote most of the comments and I tried to add an obvious example: basenameWithIndicator "Returns the basename with the indicator appended, i.e. /foo/gloops.taz basenameWithIndicator is