[squeak-dev] Re: CurrentReadOnlySourceFiles annoys me ...

Eliot Miranda eliot.miranda at gmail.com
Thu Dec 17 02:49:20 UTC 2015


Hi Levente,

On Wed, Dec 16, 2015 at 2:43 PM, Levente Uzonyi <leves at caesar.elte.hu>
wrote:

> 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.


Apart form the debugger can you think of situations in which this will
really happen?  I can't. If you can convince me that concurrent access is a
real danger then I'll think again, but in all my time doing Smalltalk with
Smalltalk-80 v2, with VisualWorks and with Croquet, Squeak and Pharo the
only time this has been an issue was in the debugger debugging source file
access.  Given that that's easy to solve I don't see the point of living
with such slow source file access for any longer :-)



>
>
> 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.
>>>
>>>
>>
>>
>


-- 
_,,,^..^,,,_
best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20151216/cbc34548/attachment.htm


More information about the Squeak-dev mailing list