Hi List,
I'm trying to use the TestMock package in a Pharo-1.1.1-OneClick image, and it uses KeyedSet. Where can I find this class? Is there any tool to lookup which package in SqueakSource contains a specific class?
Thanks in advance!
|
Try PluggableSet
http://www.mail-archive.com/pharo-project@.../msg22890.html Is there a way for you guys to deprecate deleted classes or mantain a record of deleted behaviors? (IIRC VW did this from 2.x versions) Cheers, Hernán 2011/1/14 Alex Schenkman <[hidden email]>: > Hi List, > I'm trying to use the TestMock package in a Pharo-1.1.1-OneClick image, and > it uses KeyedSet. > Where can I find this class? > Is there any tool to lookup which package in SqueakSource contains a > specific class? > Thanks in advance! |
On Jan 14, 2011, at 6:24 PM, Hernán Morales Durand wrote: > Try PluggableSet > > http://www.mail-archive.com/pharo-project@.../msg22890.html > > Is there a way for you guys to deprecate deleted classes or mantain a > record of deleted behaviors? (IIRC VW did this from 2.x versions) We try but we do not have the engineers of VW. Now find somebody that pay us just 3 engineers full time for two years and you will not recognized pharo and its process. Stef > Cheers, > > Hernán > > 2011/1/14 Alex Schenkman <[hidden email]>: >> Hi List, >> I'm trying to use the TestMock package in a Pharo-1.1.1-OneClick image, and >> it uses KeyedSet. >> Where can I find this class? >> Is there any tool to lookup which package in SqueakSource contains a >> specific class? >> Thanks in advance! > |
Hi Stef
2011/1/15 Stéphane Ducasse <[hidden email]>: > > On Jan 14, 2011, at 6:24 PM, Hernán Morales Durand wrote: > >> Try PluggableSet >> >> http://www.mail-archive.com/pharo-project@.../msg22890.html >> >> Is there a way for you guys to deprecate deleted classes or mantain a >> record of deleted behaviors? (IIRC VW did this from 2.x versions) > > We try but we do not have the engineers of VW. > Now find somebody that pay us just 3 engineers full time for two years and you will not > recognized pharo and its process. I know we are very few, but what about this idea, instead of just deleting a class we may adopt these simple rules: 1 - If deleting a class add the deleted class name somewhere (in a method?) 2 - If renaming a class, make the class to know its previous names like #previousNames (Norberto Manzanos implemented this for his own package management and I think is a great idea) doesn't require tools, just some consensus and maybe a modified #deleteClass to enforce this "policy" it sounds feasible for you? what do you think? Hernán |
Previous names is a good idea
We should adopt it! Stef On Jan 15, 2011, at 9:52 AM, Hernán Morales Durand wrote: > Hi Stef > > 2011/1/15 Stéphane Ducasse <[hidden email]>: >> >> On Jan 14, 2011, at 6:24 PM, Hernán Morales Durand wrote: >> >>> Try PluggableSet >>> >>> http://www.mail-archive.com/pharo-project@.../msg22890.html >>> >>> Is there a way for you guys to deprecate deleted classes or mantain a >>> record of deleted behaviors? (IIRC VW did this from 2.x versions) >> >> We try but we do not have the engineers of VW. >> Now find somebody that pay us just 3 engineers full time for two years and you will not >> recognized pharo and its process. > > I know we are very few, but what about this idea, instead of just > deleting a class we may adopt these simple rules: > > 1 - If deleting a class add the deleted class name somewhere (in a method?) > 2 - If renaming a class, make the class to know its previous names > like #previousNames > (Norberto Manzanos implemented this for his own package management and > I think is a great idea) > > doesn't require tools, just some consensus and maybe a modified > #deleteClass to enforce this "policy" > > it sounds feasible for you? what do you think? > > Hernán > |
In reply to this post by hernanmd
On Jan 15, 2011, at 9:52 AM, Hernán Morales Durand wrote: > Hi Stef > > 2011/1/15 Stéphane Ducasse <[hidden email]>: >> >> On Jan 14, 2011, at 6:24 PM, Hernán Morales Durand wrote: >> >>> Try PluggableSet >>> >>> http://www.mail-archive.com/pharo-project@.../msg22890.html >>> >>> Is there a way for you guys to deprecate deleted classes or mantain a >>> record of deleted behaviors? (IIRC VW did this from 2.x versions) >> >> We try but we do not have the engineers of VW. >> Now find somebody that pay us just 3 engineers full time for two years and you will not >> recognized pharo and its process. > > I know we are very few, but what about this idea, instead of just > deleting a class we may adopt these simple rules: > > 1 - If deleting a class add the deleted class name somewhere (in a method?) > 2 - If renaming a class, make the class to know its previous names > like #previousNames > (Norberto Manzanos implemented this for his own package management and > I think is a great idea) > > doesn't require tools, just some consensus and maybe a modified > #deleteClass to enforce this "policy" yes this would be nice to have tool doing it for us. > > it sounds feasible for you? what do you think? > > Hernán > |
In reply to this post by Alex Schenkman
I am probably late to the discussions here, although as the author of the TestMock package I can assert that the unit tests for TestMock pass in my pharo 1.0 environment. I have not tried the Pharo 1.1.1; and from the discussions it looks like the package fails there because KeyedSet has been deprecated. I will take a note of this, and will look forward to add a fix and publish a new version once I upgrade my Pharo image. Thanks a lot to everyone chiming in. Regards, Anindya From: Alex Schenkman <[hidden email]> To: [hidden email] Sent: Fri, January 14, 2011 3:12:54 AM Subject: [Pharo-users] Where do I find KeyedSet? Hi List, I'm trying to use the TestMock package in a Pharo-1.1.1-OneClick image, and it uses KeyedSet. Where can I find this class? Is there any tool to lookup which package in SqueakSource contains a specific class?
Thanks in advance!
|
I also noticed that the TestCase >> assert: method has changed in Pharo 1.1.1 that it does **not** take a booleanOrBlock anymore, it always expects a boolean. This would make all tests using the assert: [... a block returning boolean here ...] style fail in Pharo 1.1.1. I am not sure this change is a deliberate design decision or a bug. Whatever it is, those tests will also have to be changed as part of the TestMock port for Pharo 1.1.1 in order for the suite to pass. Regards, Anindya From: Anindya Haldar <[hidden email]> To: A friendly place where any question about pharo is welcome <[hidden email]> Sent: Thu, January 20, 2011 10:13:25 PM Subject: Re: [Pharo-users] Where do I find KeyedSet? I am probably late to the discussions here, although as the author of the TestMock package I can assert that the unit tests for TestMock pass in my pharo 1.0 environment. I have not tried the Pharo 1.1.1; and from the discussions it looks like the package fails there because KeyedSet has been deprecated. I will take a note of this, and will look forward to add a fix and publish a new version once I upgrade my Pharo image. Thanks a lot to everyone chiming in. Regards, Anindya From: Alex Schenkman <[hidden email]> To: [hidden email] Sent: Fri, January 14, 2011 3:12:54 AM Subject: [Pharo-users] Where do I find KeyedSet? Hi List, I'm trying to use the TestMock package in a Pharo-1.1.1-OneClick image, and it uses KeyedSet. Where can I find this class? Is there any tool to lookup which package in SqueakSource contains a specific class?
Thanks in advance!
|
There was a good reason for the BooleanOrBlock convention, IIRC. I wonder what it was? Something about when the assert fails, you get more information in
the debugger if you use a block. Can anyone else remember the details. Andrew From: [hidden email] [mailto:[hidden email]]
On Behalf Of Anindya Haldar I also noticed that the TestCase >> assert: method has changed in Pharo 1.1.1 that it does **not** take a booleanOrBlock anymore, it always expects a boolean. This would make all tests using the assert: [... a block returning boolean here
...] style fail in Pharo 1.1.1. I am not sure this change is a deliberate design decision or a bug. Whatever it is, those tests will also have to be changed as part of the TestMock port for Pharo 1.1.1 in order for the suite to pass. From: Anindya Haldar <[hidden email]> I am probably late to the discussions here, although as the author of the TestMock package I can assert that the unit tests for TestMock pass in my pharo 1.0 environment. I have not tried the Pharo 1.1.1; and from the discussions it looks
like the package fails there because KeyedSet has been deprecated. I will take a note of this, and will look forward to add a fix and publish a new version once I upgrade my Pharo image. From: Alex Schenkman <[hidden email]> I'm trying to use the TestMock package in a Pharo-1.1.1-OneClick image, and it uses KeyedSet. Where can I find this class? Is there any tool to lookup which package in SqueakSource contains a specific class? Thanks in advance!
|
In reply to this post by Anindya Haldar
Thanks!
Stef On Jan 21, 2011, at 7:13 AM, Anindya Haldar wrote: > I am probably late to the discussions here, although as the author of the TestMock package I can assert that the unit tests for TestMock pass in my pharo 1.0 environment. I have not tried the Pharo 1.1.1; and from the discussions it looks like the package fails there because KeyedSet has been deprecated. I will take a note of this, and will look forward to add a fix and publish a new version once I upgrade my Pharo image. > > Thanks a lot to everyone chiming in. > > Regards, > Anindya > > From: Alex Schenkman <[hidden email]> > To: [hidden email] > Sent: Fri, January 14, 2011 3:12:54 AM > Subject: [Pharo-users] Where do I find KeyedSet? > > Hi List, > > I'm trying to use the TestMock package in a Pharo-1.1.1-OneClick image, and it uses KeyedSet. > Where can I find this class? > Is there any tool to lookup which package in SqueakSource contains a specific class? > > Thanks in advance! > > |
In reply to this post by Anindya Haldar
> I also noticed that the TestCase >> assert: method has changed in Pharo 1.1.1 that it does **not** take a booleanOrBlock anymore, it always expects a boolean. This would make all tests using the assert: [... a block returning boolean here ...] style fail in Pharo 1.1.1. I am not sure this change is a deliberate design decision or a bug. Whatever it is, those tests will also have to be changed as part of the TestMock port for Pharo 1.1.1 in order for the suite to pass. This is a deliberated change. Stef > > Regards, > Anindya > > From: Anindya Haldar <[hidden email]> > To: A friendly place where any question about pharo is welcome <[hidden email]> > Sent: Thu, January 20, 2011 10:13:25 PM > Subject: Re: [Pharo-users] Where do I find KeyedSet? > > I am probably late to the discussions here, although as the author of the TestMock package I can assert that the unit tests for TestMock pass in my pharo 1.0 environment. I have not tried the Pharo 1.1.1; and from the discussions it looks like the package fails there because KeyedSet has been deprecated. I will take a note of this, and will look forward to add a fix and publish a new version once I upgrade my Pharo image. > > Thanks a lot to everyone chiming in. > > Regards, > Anindya > > From: Alex Schenkman <[hidden email]> > To: [hidden email] > Sent: Fri, January 14, 2011 3:12:54 AM > Subject: [Pharo-users] Where do I find KeyedSet? > > Hi List, > > I'm trying to use the TestMock package in a Pharo-1.1.1-OneClick image, and it uses KeyedSet. > Where can I find this class? > Is there any tool to lookup which package in SqueakSource contains a specific class? > > Thanks in advance! > > > |
Although I can see TestCase >> #assert:description: and #assert:description:resumable take aBooleanOrBlock as an argument. Isn't the boolean only argument expectation for #assert: kind of inconsistent with these? Regards, Anindya From: Stéphane Ducasse <[hidden email]> To: A friendly place where any question about pharo is welcome <[hidden email]> Sent: Fri, January 21, 2011 11:32:02 AM Subject: Re: [Pharo-users] Where do I find KeyedSet? > I also noticed that the TestCase >> assert: method has changed in Pharo 1.1.1 that it does **not** take a booleanOrBlock anymore, it always expects a boolean. This would make all tests using the assert: [... a block returning boolean here ...] style fail in Pharo 1.1.1. I am not sure this change is a deliberate design decision or a bug. Whatever it is, those tests will also have to be changed as part of the TestMock port for Pharo 1.1.1 in order for the suite to pass. This is a deliberated change. Stef > > Regards, > Anindya > > From: Anindya Haldar <[hidden email]> > To: A friendly place where any question about pharo is welcome <[hidden email]> > Sent: Thu, January 20, 2011 10:13:25 PM > Subject: Re: [Pharo-users] Where do I find KeyedSet? > > I am probably late to the discussions here, although as the author of the TestMock package I can assert that the unit tests for TestMock pass in my pharo 1.0 environment. I have not tried the Pharo 1.1.1; and from the discussions it looks like the package fails there because KeyedSet has been deprecated. I will take a note of this, and will look forward to add a fix and publish a new version once I upgrade my Pharo image. > > Thanks a lot to everyone chiming in. > > Regards, > Anindya > > From: Alex Schenkman <[hidden email]> > To: [hidden email] > Sent: Fri, January 14, 2011 3:12:54 AM > Subject: [Pharo-users] Where do I find KeyedSet? > > Hi List, > > I'm trying to use the TestMock package in a Pharo-1.1.1-OneClick image, and it uses KeyedSet. > Where can I find this class? > Is there any tool to lookup which package in SqueakSource contains a specific class? > > Thanks in advance! > > > |
> Although I can see TestCase >> #assert:description: and #assert:description:resumable take aBooleanOrBlock as an argument. Isn't the boolean only argument expectation for #assert: kind of inconsistent with these? probably an inconsistency but not quite so since for resumable it should be a block to be able to restart. Stef |
Free forum by Nabble | Edit this page |