Hello,
I have installed the package CollectionExtension to my Pharo3.0 image (i have the latest image) but there is a test that it stopped working.
There is a bug in Collection>>includesAllOf:
if i do "#(#1 #2) includesAllOf: #(#1 #1)" it returns false.
Do i have to install something else?
I know that in the latest image of moose this bug was fix.
Thanks!
On Fri, Jun 7, 2013 at 4:54 PM, Sebastian Tleye stleye@gmail.com wrote:
Do i have to install something else?
I know that in the latest image of moose this bug was fix.
this is important because Pharo wants to include Moose's Collection Extensions.
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
On Fri, Jun 7, 2013 at 4:54 PM, Sebastian Tleye stleye@gmail.com wrote:
Hello,
I have installed the package CollectionExtension to my Pharo3.0 image (i have the latest image) but there is a test that it stopped working.
There is a bug in Collection>>includesAllOf:
if i do "#(#1 #2) includesAllOf: #(#1 #1)" it returns false.
Do i have to install something else?
I know that in the latest image of moose this bug was fix.
Latest version with Moose runs on pharo 2.0 and since you are testing it on 3.0, this might have made the difference. May be you can first load CollectionExtension in 2.0 to see there might be breaking it in pharo3.0.
Thanks!
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I have just tried installing CollectionExtensions in pharo 2.0 but it's still not working.
2013/6/7 Usman Bhatti usman.bhatti@gmail.com
On Fri, Jun 7, 2013 at 4:54 PM, Sebastian Tleye stleye@gmail.com wrote:
Hello,
I have installed the package CollectionExtension to my Pharo3.0 image (i have the latest image) but there is a test that it stopped working.
There is a bug in Collection>>includesAllOf:
if i do "#(#1 #2) includesAllOf: #(#1 #1)" it returns false.
Do i have to install something else?
I know that in the latest image of moose this bug was fix.
Latest version with Moose runs on pharo 2.0 and since you are testing it on 3.0, this might have made the difference. May be you can first load CollectionExtension in 2.0 to see there might be breaking it in pharo3.0.
Thanks!
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev