<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks for the reply! Even if #nextObject & Co. do not have a real use case, I think they should be protected. It is kind of annoying for any Squeak beginner like me to "try out a method" and thereby get the whole image crashed. Would it be the right solution
to override #nextObject and #nextInstance both in Number and Character by returning self shouldNotImplement?</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
By the way, if these selectors are obsoleted, why aren't they moved to any Deprecated package?</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Christoph</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>Von:</b> Vm-dev <vm-dev-bounces@lists.squeakfoundation.org> im Auftrag von Levente Uzonyi <leves@caesar.elte.hu><br>
<b>Gesendet:</b> Freitag, 19. Juli 2019 01:05 Uhr<br>
<b>An:</b> Open Smalltalk Virtual Machine Development Discussion <vm-dev@lists.squeakfoundation.org><br>
<b>Betreff:</b> Re: [Vm-dev] $x nextObject</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText"><br>
No immediate object should ever receive #nextObject. I think the new <br>
immediates (Character, SmallFloat64) lack the #shouldNotImplement <br>
implementation. Same goes for #nextInstance.<br>
<br>
Btw, #nextObject was obsoleted by the segmented memory model. Perhaps it <br>
can still answer something, but you won't be able to iterate over all <br>
objects with it. If that's what you want, then you should use #allObjects <br>
instead.<br>
<br>
Levente<br>
<br>
On Thu, 18 Jul 2019, Christoph Thiede wrote:<br>
<br>
> <br>
> Hello,<br>
><br>
> is it a known bug that the Squeak VM may crash when you perform #nextObject<br>
> on any Character object? I can reproduce this issue on multiple Windows 10<br>
> machines, using SqueakCog 201810071412. I am familiar not at all with the VM<br>
> implementation, but for example, after evaluating $x nextObject, the used<br>
> RAM strongly reduces and after a few seconds, the process terminates.<br>
><br>
> Kind regards,<br>
> Christoph<br>
><br>
><br>
><br>
> --<br>
> Sent from: <a href="http://forum.world.st/Squeak-VM-f104410.html">http://forum.world.st/Squeak-VM-f104410.html</a><br>
</div>
</span></font></div>
</body>
</html>