Ok....I finally take an hour and fix all the Nile tests in Pharo 1.1. They are now all green. While doing this, I have removed all (or all I saw) from uniClasses in Nile.

It would be very cool if someone from Nile can check my latests commits in the repository.

If you want to load it:

Gofer new
��� squeaksource: 'MetacelloRepository';
��� package: 'ConfigurationOfNile';
��� load.

and then

(ConfigurationOfNile project version: '1.1') load: 'Core Tests'�


Cheers

Mariano



On Sat, May 22, 2010 at 6:37 PM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
Yes we should just update Nile
This is a clear example of the fact that since we do not record refactoring external packages can easily degrade



On May 22, 2010, at 6:26 PM, Alexandre Bergel wrote:

> I have the feeling that all these uniClasses are stone age. All traces should be removed.
>
> Cheers,
> Alexandre
>
>
> On 22 May 2010, at 13:19, Mariano Abel Coca wrote:
>
>> Hi,
>>
>> I've found a few senders of #isSystemDefined when trying to run the pharo dev test suite, and I don't know what is the expected behavior.
>>
>> I've read in: http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg12075.html that the idea is to remove the message and all it's senders, but I don't know why is used here in Nile.
>>
>> The senders are in NSSmartRefStream, inside of #uniClassInstVarsRefs:, #uniClasesDo: and #beginInstance:size:
>>
>> Any hint on this will be appreciated.
>>
>> Cheers,
>>
>> Mariano.
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project