[Pharo-dev] [Pharo 7.0-dev] Build #176: 20505-The-special-objects-array-needs-to-be-recreated-during-bootstrap

Guillermo Polito guillermopolito at gmail.com
Tue Oct 10 08:04:30 EDT 2017

Hi Pavel,

I don't like this change.

First, there is no comment nor explanation why that is needed. This change
is obscure, if we forget in a couple of months why that line of code is
there we may
 - delete it unintentionally
 - or leave it forever and fear to clean it up because we do not understand
it :(

Second, It looks that recreating the special objects array there, like
that, means that it was not correctly created from the beginning. We should
instead create it correctly from the beginning.

I think we should revert this change.

On Tue, Oct 10, 2017 at 12:24 PM, <ci-pharo-ci-jenkins2 at inria.fr> wrote:

> There is a new Pharo build available!
> The status of the build #176 was: SUCCESS.
> The Pull Request #336 was integrated: "20505-The-special-objects-
> array-needs-to-be-recreated-during-bootstrap"
> Pull request url: https://github.com/pharo-project/pharo/pull/336
> Issue Url: https://pharo.fogbugz.com/f/cases/20505
> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%
> 20pull%20request%20and%20branch%20Pipeline/job/development/176/


Guille Polito

Research Engineer

Centre de Recherche en Informatique, Signal et Automatique de Lille

CRIStAL - UMR 9189

French National Center for Scientific Research - *http://www.cnrs.fr

*Web:* *http://guillep.github.io* <http://guillep.github.io>

*Phone: *+33 06 52 70 66 13
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20171010/04b056b2/attachment-0002.html>

More information about the Pharo-dev mailing list