[Pharo-dev] [update 3.0] #30338

Stéphane Ducasse stephane.ducasse at inria.fr
Wed Aug 21 11:59:52 EDT 2013


On Aug 21, 2013, at 5:44 PM, Camillo Bruni <camillobruni at gmail.com> wrote:

> On 2013-08-21, at 17:37, Stéphane Ducasse <stephane.ducasse at inria.fr> wrote:
>>>> There are some problems in NativeBoost if a method does not belong to the
>>>> class itself, i don't understand the problem very well but that is what
>>>> Igor and Stef told me.
>> 
>> 
>> Some methods are placeholder for generated code and the placeholder cannot be avoided and there is nothing wrong in the design.
>> 
>> This is why such system wide tests should be replaced by rules that each package declare as false positive and adapt to the package own 
>> practice. 
> 
> but that doesn't justify that the methods have the same contents, AFAIK this is what the test compares.

so do you think that we should generate method 
value
	 'foo1' 

value
	'foo2' 

value 
	'foo3' 

just to satisfy a test that does not apply?

> 
> And I still think form a outside viewpoint duplicated methods do not make sense at all, NativeBoost should be no exception there.
> 
> 





More information about the Pharo-dev mailing list