On Friday, July 7, 2017 at 5:23:21 AM UTC-5, Edward K. Ream wrote: > > I'm beginning to wonder what the difference is between the Pharo way and > #511: > reload-leo command. <https://github.com/leo-editor/leo-editor/issues/511> > > How does Pharo handle changes in object format or methods? How does Pharo > recover from crashes due to changed method signatures, invalid calls, etc? >
This simple, deep video <https://vimeo.com/channels/ndc2014/97315968> shows how at around 3:30. It illustrates a great quote at 5:40: "Objects are not there just to run whatever we put in classes. Objects are there to carry on a dialog with us as programmers." Hmm. Roughly two minutes to change your world. So...Could we define a PharoObject class (in Python) that could do the same? Has anyone already done so? A quick google has not turned up anything. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
