Kind of related - we did get the ability to save methods with undefined classes and undeclared variables (vs having to correct this to save). So at least a nod to that?

Tim

Sent from my iPhone

On 13 Sep 2018, at 08:22, Guillermo Polito <guillermopolito@gmail.com> wrote:

Well it's just a matter of stability, we were too concentrated with other stuff.
But I fear that this would be a too disrupting change to apply now in Pharo 7...

We were thinking that our focus before the release should be:
 - fix the important bugs out there (so, everybody, please raise/report your issues :))
 - iterate on Calypso a bit more so we fix some usability glitches

On Thu, Sep 13, 2018 at 4:58 PM Esteban Lorenzano <estebanlm@gmail.com> wrote:
We didn't have the time to work on it.
It is still part of the roadmap (since we need it to dream with a nice module system), but it will probably arrive in P8.

Esteban

On Thu, Sep 13, 2018 at 4:51 PM Torsten Bergmann <astares@gmx.de> wrote:
At ESUG 207 there was a presentation about UndefinedClasses as first class entities.

According to the slides:

https://de.slideshare.net/esug/firstclass-undefined-classes-for-pharo-from-alternative-designs-to-a-unified-practical-solution

this was planned for inclusion into Pharo 7.

Is this still on the plate? Any status?

Thanks
T.



--

   

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

Phone: +33 06 52 70 66 13