<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Dave!<div><br></div><div>Thanks. :-)</div><div><br></div><div>Considering a bigger but similar, maybe FFI-based, mechanism, do you think it makes sense to clean up such things on a fresh startup only instead of every snapshot? Think of flushing the entire GPU-state you are currently managing just to retain some other in-image object. Seems overkill.</div><div><br></div><div>What's the underlying best practice? :-)</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 28.05.2020 15:26:09 schrieb David T. Lewis <lewis@mail.msen.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">On Wed, May 27, 2020 at 08:58:48AM +0200, Marcel Taeumel wrote:<br>> Hi, there. :-)<br>> <br>> Why do we reset file-related stuff (e.g. source file handles, default directory class)?? on every snapshot? Shouldn't there be a check for "resuming" (or "quitting") in FileDirectory class >> #startUp(:) (and #shutDown(:))?<br>> <br>> ...or am I missing something? Tim (tpr)! You started it in 2003. Please, explain.??:-D<br>> <br>> Maybe ... we don't ever want to store dangling source-file handles in the image?<br>> <br><br>Yes I think that is the reason. The image snapshot should contain little or<br>no platform-specific stuff, and there is no point in allowing it to contain<br>obsolete file handles that would need to be detected by primitive fallback<br>code when the snapshot is next loaded.<br><br>After all, the image that you snapshot today may next be opened by someone<br>with a Risc OS computer :-)<br><br>Dave<br><br></div></blockquote>
</div></body>