Issue 786 in moose-technology: MooseQueryResult>>intersection: is broken

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 786 in moose-technology: MooseQueryResult>>intersection: is broken

moose-technology
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-MooseTools

New issue 786 by [hidden email]: MooseQueryResult>>intersection: is  
broken
http://code.google.com/p/moose-technology/issues/detail?id=786

calling intersection between two MooseQueryResult produces an error  
because "MooseQueryResult is not a variable type"

This is raised in basicNew:

A possible workaround is to redefine MooseQueryResult>>intersection:  
aCollection
        | result |
       
        result := self class new.
       
        aCollection do: [ :each|
                ((self includes: each) and: [(result includes: each) not])
                                ifTrue: [ result add: each]].
               
        ^ result

But it might not be the best solution since I assume basicNew: might be  
called from other methods ...


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 786 in moose-technology: MooseQueryResult>>intersection: is broken

moose-technology
Updates:
        Labels: Milestone-4.7 Component-Famix

Comment #2 on issue 786 by [hidden email]:  
MooseQueryResult>>intersection: is broken
http://code.google.com/p/moose-technology/issues/detail?id=786

(No comment was entered for this change.)

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev