On 20/5/14 04:41, Rick Kitts wrote:
Hello. I was wondering if anyone could point me to or otherwise
suggest some best practices for working on Kernel code. I’m futzing
about with the Duration class (in the interest of fixing 13215)
Thanks!
and have discovered that it’s really easy to crash Pharo if I break
that class. I assume there are other classes that would exhibit the
same behavior.
Yes like Array or OrderedCollection.
We are working on a bootstrap of pharo and it could help for brain
surgery (but in that case the system may simply not build at all).
So the suggestion of Ron to use ChangeSet is a good one.
Now once I got change that crash (just a tight endless loop) as soon as
you change anything and there you have to rollback and turn around the
self referencing aspect.
I suppose I could just be really cautious and save my image after
every change but that seems so error prone that I’m hoping that there
are idiomatic ways of working on kernel code (beyond just save ones
image early and often) so I don’t lose work. I’m asking because the
naive solution (copy the original class, modify it to suit, delete the
original and rename the new class to the original) of course doesn’t work.
TIA for any suggestions or assistance and apologies in advance if this
is RTFM, I didn’t see anything (didn’t look very hard either though).
—Rick
