On Thu, Sep 13, 2018 at 11:07 PM Tim Mackinnon wrote:
> 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?
>
Yes, I was following your progress there :)
And since you have pr
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 wrote:
>
> Well it's just a matter of stability, we we
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
yo
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 wrote:
> At ESUG 207 there was a presentation about UndefinedClasses as first
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 sti