On Thu, Jan 20, 2022 at 11:43:08AM -0800, Eliot Miranda wrote:
> Hi All,
> 
> > On Jan 19, 2022, at 12:38 AM, Marcel Taeumel <marcel.taeumel at hpi.de> wrote:
> > 
> > ???
> > Hi Dave --
> > 
> > > [...] which point the sources file no longer lives on rotating media
> > 
> > Quick comment on this one. :-) Many computers use SSD/Flash storage these days and I am pretty sure that modern operating systems have their tricks with caching bigger files even further without the application ever noticing. However, considering external file scanners scanning for viruses, yes, it can be beneficial to avoid an extra use of some OS file API.
> > 
> 
> Again our performance issues accessing sources on windows are much more likely to be rooted in the absurdity of opening a file for every file access, using the ugly CurrentReadOnlySources nonsense to compensate.  If we were to maintain the in-image source files correctly our performance would improve markedly.
> 
> The issue with source files is fundamentally to do with providing a way for the debugger to access source through different files while debugging source file access.  A substituteSourceFilesDuring: aBlock protocol would work, be infinitely preferable than cacheDuring:.  Why are we still unable to do something constructive here?

Hi Eliot,

I opened this thread to discuss something else. If anyone has
tried loading DTL-internal-sources-dtl.4.mcz from the inbox, I
would be interested to hear what you think of the idea after
trying it in your image. But please respond only if you have
actually tried it :-)

To the question "Why are we still unable to do something
constructive here?", I believe you are referring to the discussion
that was taking place in the "Proper use of SourceFiles and
"CurrentReadOnlySourceFiles cacheDuring:"" thread. Levente
advocated using process local variables, and you advocated
the protocol that you mention above.

Levente: http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-January/218110.html

Eliot: http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-January/218111.html

I don't know which approach would be better. As far as I know
neither proposal has been implemented.

Dave