<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Hi all,</p>
<p><br>
</p>
<p></p>
<div>I just took a short look at all references to the #World binding in my main image, and there are several packages that would probably break if we completely dropped this binding: <a href="https://github.com/hpi-swa/animations/" class="x_x_OWAAutoLink">Animations</a>, <a href="https://github.com/cmfcmf/MagicMouse/" class="x_x_OWAAutoLink">MagicMouse</a>, <a href="https://github.com/hpi-swa-teaching/Morphic-Testing-Framework" class="x_x_OWAAutoLink">Morphic Testing Framework</a>, RefactoringTools, <a href="https://github.com/tom95/Pheno" class="x_x_OWAAutoLink">Pheno</a>, <a href="https://github.com/hpi-swa-teaching/SwaLint" class="x_x_OWAAutoLink">SwaLint</a>, <a href="https://github.com/hpi-swa/signals" class="x_x_OWAAutoLink">Signals</a>, <a href="https://github.com/hpi-swa/widgets" class="x_x_OWAAutoLink">Widgets</a>, <a href="https://github.com/hpi-swa-teaching/WindowAcrobatics" class="x_x_OWAAutoLink">WindowAcrobatics</a>.
And this enumeration does neither yet include my own projects nor all other valuable packages I do not know yet. Even the trunk itself still somehow depends on #World, see HandMorph >> #objectForDataStream: or DiskProxy >> #comeFullyUpOnReload:.<br>
</div>
<br>
<p></p>
<p>I would really wish we could find a solution to raise a DeprecationWarning if the binding is still accessed but still provide a fallback for it. Compiler support sounds interesting as well, but we should notice that existing images should still keep working
without reinstalling/patching any package. Hypothetically, we could change the Compiler (*not* the Parser) to compile a deprecated literal binding from an extra list differently, so that the source code still will look the same, but the binding will actually
point to a method call. Or would such a source code/bytecode discrepancy be too confusing for other components such as the decompiler?</p>
<p><br>
</p>
<p>Please note that this problem is not only applicable to the World global. Whenever we decide to deprecate a class, we could benefit from a solution that raises a DeprecationWarning when an attempt is made to access it as well.</p>
<p><br>
</p>
<p>Best,</p>
<p>Christoph</p>
<div id="x_Signature">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:rgb(0,0,0); font-family:Calibri,Helvetica,sans-serif,EmojiFont,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols">
<div name="x_divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div>
<div class="x__rp_T4" id="x_Item.MessagePartBody">
<div class="x__rp_U4 x_ms-font-weight-regular x_ms-font-color-neutralDark x_rpHighlightAllClass x_rpHighlightBodyClass" id="x_Item.MessageUniqueBody" style="font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont">
<div dir="ltr">
<div id="x_divtagdefaultwrapper"><font face="Calibri,Helvetica,sans-serif,EmojiFont,Apple Color Emoji,Segoe UI Emoji,NotoColorEmoji,Segoe UI Symbol,Android Emoji,EmojiSymbols">
<div id="x_Signature">
<div style="margin:0px"><font style="font-family:Calibri,Arial,Helvetica,sans-serif,serif,EmojiFont">
<div><font size="3" color="black"><span style="font-size:12pt"><a href="http://www.hpi.de/" target="_blank" rel="noopener noreferrer" id="LPNoLP"><font size="2"><span id="LPlnk909538"><font color="#757B80"></font></span></font></a></span></font></div>
</font></div>
</div>
</font></div>
</div>
</div>
</div>
</div>
<div><font size="2" color="#808080"></font></div>
</div>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von K K Subbu <kksubbu.ml@gmail.com><br>
<b>Gesendet:</b> Sonntag, 13. September 2020 13:38:10<br>
<b>An:</b> squeak-dev@lists.squeakfoundation.org<br>
<b>Betreff:</b> Re: [squeak-dev] The Inbox: System-dtl.1170.mcz</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On 12/09/20 6:52 pm, commits@source.squeak.org wrote:<br>
> End of the #World as we know it. Package postscript only. About two<br>
> years ago we eliminated all dependencies on global World. However,<br>
> the global binding has remained functional on the theory that some<br>
> external packages might still expect it.<br>
When an undefined global var is encountered, is it possible to detect it <br>
as an obsolete reference and then offer an option to replace it with a <br>
proper object accessor? Perhaps a 'Obsolete Globals' dictionary mapping <br>
an obsolete global symbol to an object access?<br>
<br>
Currently, we just throw up a 'Undefined Variable' dialog offering <br>
closest symbols to correct a possible misspelling.<br>
<br>
Regards .. Subbu<br>
<br>
</div>
</span></font>
</body>
</html>