[squeak-dev] The Inbox: System-ct.1236.mcz

christoph.thiede at student.hpi.uni-potsdam.de christoph.thiede at student.hpi.uni-potsdam.de
Mon Aug 30 18:16:56 UTC 2021


Hi Marcel,

please see ST80-ct.271. :-)

Best,
Christoph

---
Sent from Squeak Inbox Talk

On 2021-06-16T13:28:19+02:00, marcel.taeumel at hpi.de wrote:

> Hi Christoph.
> 
> > Do you think we should instead modify StandardSystemView >> #initialFrame to use #currentWorld instead of "nil" or are there any semantic differences?
> 
> Yes, I think we should fill those "nil" cases with "self currentWorld". Well, there are of course protocols that work with a morph not being in any world. Yet, there are some protocols that expect a world where "self currentWorld" should be good enough. We should just be careful to not put such morphs into the currentWorld by accident.
> 
> Best,
> Marcel
> Am 16.06.2021 13:01:18 schrieb christoph.thiede at student.hpi.uni-potsdam.de <christoph.thiede at student.hpi.uni-potsdam.de>:
> Hi Marcel,
> 
> > -1
> >
> > It makes no sense to officially support a "nil" argument in this protocol.
> 
> partially it was already supported officially before (some parameters already were named "aWorldOrNil").
> 
> Do you think we should instead modify StandardSystemView >> #initialFrame to use #currentWorld instead of "nil" or are there any semantic differences?
> 
> Best,
> Christoph
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210616/445e5ea1/attachment.html>
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210830/c31c49b8/attachment.html>


More information about the Squeak-dev mailing list