My objection is that concurrent access of the read-only source files would 
cause race conditions.
We might simplify the thing by using the regular source files (or some 
shared read-only copies) when requested from the UI process, and create a 
read-only copy for all other processes. That would cover most potential 
slow-downs in the Trunk.

Levente

On Wed, 16 Dec 2015, Eliot Miranda wrote:

> Hi all,
>
>    IMO we don't need CurrentReadOnkySourceFiles, instead we should have SourceFilesArray maintain one read-only copy per source file.  The objection is that using a single file will make debugging source file access break, since the debuggers own access to source will perturb the source files whose access is being debugged, but the debugger can easily temporarily install a different read-init copy whenever it accesses source, insulating the debugged code from this effect.
>
> _,,,^..^,,,_ (phone)
>
>> On Dec 16, 2015, at 4:38 AM, marcel.taeumel <Marcel.Taeumel at hpi.de> wrote:
>>
>> I want to catch all exceptions because it is kind of test code where only
>> success matters. :-)  It is an experiment where the participants should
>> program stuff and receive a green tick whenever the task is accomplished.
>> Raising a debugger when the participant puts a "self halt" or anything into
>> the control flow of the test code would confuse the participant.
>>
>> Conceptionally, CurrentReadOnlySourceFiles is no kind of an exception. Thank
>> you for the explanation. Can you sketch the steps to transform that into a
>> PLV? Why would it take some effort?
>>
>> Bset,
>> Marcel
>>
>>
>>
>> --
>> View this message in context: http://forum.world.st/CurrentReadOnlySourceFiles-annoys-me-tp4867253p4867327.html
>> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>>
>
>