Guys - youâre awesome! It really shows why our environment is so powerful and why more people need to think this way! For back porting - you donât need to, as for exercism we are loading a script anyway, so I can load in some code until weâre ready for 7.0 I do agree that infinite debuggers is a pressing problem too (and sorry to distract on that one). Still - we want to present our best face when we go live on exercism - and the pharo features list I copied from Pharo.org (slightly tweaked) drove me to live up to the Hugh standards we set ourselves. Iâll definitely try out what youâve all proposed - I figured if was all possible . Tim Sent from my iPhone
On 9 Aug 2018, at 11:02, Marcus Denker <marcus.denker@inria.fr> wrote:
On 9 Aug 2018, at 10:59, Guillermo Polito <guillermopolito@gmail.com> wrote:
Hi Marcus,
Is it wise to backport things that may break things like this? maybe not, but it just took 5 minutes as it is very simple
I'd prefer to put the energy on backporting the workaround to avoid the infinite debuggers...
Yes.
On Thu, Aug 9, 2018 at 10:50 AM Marcus Denker <marcus.denker@inria.fr> wrote:
2) when coding - if you want reference a missing class, why donât we let you? TonelReader seems to do it, why canât the editor? (This probably applies to variables as well - show them broken, let me fix it when I choose. The iVar case is a little rarer - although I hate the way we prompt fix, prompt fix instead of doing it in one go - itâs very old fashioned)
This is fixed in Pharo7: we added a menu entry âleave undeclaredâ as the first option: <leave undeclared.png>
Does anyone have tips on solving these? It spoils the exercism experience that I thought we could convey, so Iâd like to at least fix #1 in 6.1 if I can.
I will back port the fix for 2) to Pharo6 and will do a quick prototype for 1)
https://pharo.fogbugz.com/f/cases/22305/Backport-to-Pharo6-Leave-Variable-Un...
Marcus
--
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