Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- 3 participants
- 144636 messages
Re: [Pharo-dev] RB Tests failing
by Nicolai Hess
2014-09-30 11:02 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>:
> Hi,
>
> now when you download a new Pharo4 image there are 3 tests
> failing/erroring:
> Failures:
> RBRenameInstanceVariableTest>>#testRenameInstVarAccessorsReferences
>
> Errors:
> RBRemoveClassTest>>#testRemoveClass
> RBExtractMethodTest>>#testExtractMethodThatMovesTemporaryVariable
>
> Is there an issue about that? Is anybody looking into it?
>
Yes there are
13718
13719
13588
Mark Rizun worked on them, but the fix does not work resp. I can not
find a slice.
>
> Uko
>
>
Sept. 30, 2014
Re: [Pharo-dev] RB Tests failing
by Max Leske
On 30.09.2014, at 11:02, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote:
> Hi,
>
> now when you download a new Pharo4 image there are 3 tests failing/erroring:
> Failures:
> RBRenameInstanceVariableTest>>#testRenameInstVarAccessorsReferences
>
> Errors:
> RBRemoveClassTest>>#testRemoveClass
> RBExtractMethodTest>>#testExtractMethodThatMovesTemporaryVariable
>
> Is there an issue about that? Is anybody looking into it?
>
> Uko
>
I was going to, havenât checked th open issues yet
Sept. 30, 2014
RB Tests failing
by Yuriy Tymchuk
Hi,
now when you download a new Pharo4 image there are 3 tests failing/erroring:
Failures:
RBRenameInstanceVariableTest>>#testRenameInstVarAccessorsReferences
Errors:
RBRemoveClassTest>>#testRemoveClass
RBExtractMethodTest>>#testExtractMethodThatMovesTemporaryVariable
Is there an issue about that? Is anybody looking into it?
Uko
Sept. 30, 2014
Re: [Pharo-dev] Implementing lazy loading for expandable collections
by Max Leske
A similar implementation is possible for HashedCollection:
HashedCollection class>>new
^ self basicNew
initialize: 1 â<âââââââââ initialize to 1 instead of 5"
HashedCollection>>grow
"Grow the elements array and reinsert the old elements"
| oldElements |
oldElements := array.
array := Array new: (HashTableSizes atLeast: self growSize). â<âââââââââ use #growSize here"
tally := 0.
oldElements
do:
[ :each |
each == nil
ifFalse: [ self noCheckAdd: each ] ]
HashedCollection>>growSize
"Answer what my next higher table size should be"
^HashTableSizes atLeast: self capacity * 3 // 2 + 5 â<âââââââââ increased from +2 to +5â
Iâm not really sure about this change though. HashedCollections are a bit more complicated and maybe itâs ok to initialize them with 5?
Also: there are a few subclasses (e.g. MethodDictionary) that need extra attention (they override various methods like #grow, #growTo:, #newâ¦).
BTW: initializing HashedCollections with 0 doesnât work because not all methods correctly check the array size and just assume that at least one element can be added.
On 30.09.2014, at 10:13, Max Leske <maxleske(a)gmail.com> wrote:
> I just did a quick implementation with your idea in mind. The implementation is very easy and looks like this:
>
> OrderedCollection class>>new
> ^ self new: 0
>
> OrderedCollection>>growSize
> ^ array size max: 10
>
> I changed #growSize so that the first grow will end up having the same size the #new would create previously. Otherwise the number of grows would be very high for small collections. This change saves a factor 4 of space on new OrderedCollections (Array new sizeInMemory â> 4, (Array new: 10) sizeInMemory â> 44).
>
> Using nil instead of an empty array would achieve memory savings of factor 14, but with the extra message sends and initialization logic (and the extra instance variable) I think that factor 10 is good enough.
> What do you think?
>
> Cheers,
> Max
>
>
> On 30.09.2014, at 09:43, Max Leske <maxleske(a)gmail.com> wrote:
>
>> Hi Alex,
>>
>> I want to improve my lazy loading implementation and I was hoping to get your feedback. So I hope you donât mind if I forward this message from the original thread to you.
>>
>> Cheers,
>> Max
>>
>> Begin forwarded message:
>>
>>> From: Max Leske <maxleske(a)gmail.com>
>>> Subject: Re: [Pharo-dev] Implementing lazy loading for expandable collections
>>> Date: 22. September 2014 14:06:55 MESZ
>>> To: Pharo Development List <pharo-dev(a)lists.pharo.org>
>>>
>>>
>>> On 20.09.2014, at 14:27, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>>>
>>>> Hi Max!
>>>>
>>>> Thanks! This is something I wanted to push to Pharo for a long time. A simpler approach, would be to initialize the internal array to #() when initialized per default. This will provide pretty much the same benefits, and will not break the existing tools.
>>>>
>>>> Does this make sense to you?
>>>
>>> I think that would work well for standard use cases with #new. However, it wouldnât work for explicit size requests. The question of course is, how often will a collection be created with an explicit size and *still* stay empty. I guess you would know that better than me.
>>>
>>> I opted for the other solution because I didnât want to change the meaning of #new (which is to request a default size of 10) and because I simply assumed that even collections with explicitly requested size could stay empty.
>>>
>>> In terms of simplicity I like youâre idea far better of course :) It also makes a lot of changes moot that are necessary to initialize the array when required, because the array will simply be grown.
>>>
>>> What do your measurements say?
>>>
>>> Cheers,
>>> Max
>>>
>>>>
>>>> Alexandre
>>>>
>>>>> Le 19-09-2014 à 2:35, Max Leske <maxleske(a)gmail.com> a écrit :
>>>>>
>>>>> Iâve written an implementation of lazily initialized expandable collections (for OrderedCollection and subclasses only for now), inspired by Alexandreâs talk at ESUG (http://www.youtube.com/watch?v=x0YJ2dsZdKg&list=UUO-vBhaKVZf0al-ISMMPvRw) The implementation is pretty much straight forward but there are a couple of culprits I want to point out in case anybody else wants to do this:
>>>>>
>>>>> - my implementation requires an extra instance variable in OrderedCollection to store the requested size. This extra instance variable will break Monticello (and possibly other tools) because Monticello uses OrderedCollections to load code and the particular way it uses them makes it impossible to change the number of instance variables on OrderedCollection. Also, all .mcz files written after the change will not be loadable by images without the new instance variable (same reason).
>>>>> - the above means that you have to modify the code in the image manually and save a new âbase image"
>>>>> - read only messages should obviously not initialize the array. The âfirstIndexâ and âlastIndexâ variables are quite handy for that. I initialize those variables to 1 and 0 respectively which makes most things work already (e.g. #size, #isEmpty etc.).
>>>>> - when trying to implement the same for HashedCollection I couldnât. The image didnât just stop working, there was no output at all on the console, not even when using a debug VM. The problem seems to be MethodDictionary, at least thatâs the only subclass of Dictionary for which adding an instance variable doesnât work.
>>>>>
>>>>> Iâll share some memory monitoring as soon as I have something significant (only just rolled it out).
>>>>>
>>>>>
>>>>> Big thanks to Alex for his talk and the cool work he and his students did!
>>>>>
>>>>> Cheers,
>>>>> Max
>>>>
>>>
>>
>
Sept. 30, 2014
Re: [Pharo-dev] Implementing lazy loading for expandable collections
by Max Leske
I just did a quick implementation with your idea in mind. The implementation is very easy and looks like this:
OrderedCollection class>>new
^ self new: 0
OrderedCollection>>growSize
^ array size max: 10
I changed #growSize so that the first grow will end up having the same size the #new would create previously. Otherwise the number of grows would be very high for small collections. This change saves a factor 4 of space on new OrderedCollections (Array new sizeInMemory â> 4, (Array new: 10) sizeInMemory â> 44).
Using nil instead of an empty array would achieve memory savings of factor 14, but with the extra message sends and initialization logic (and the extra instance variable) I think that factor 10 is good enough.
What do you think?
Cheers,
Max
On 30.09.2014, at 09:43, Max Leske <maxleske(a)gmail.com> wrote:
> Hi Alex,
>
> I want to improve my lazy loading implementation and I was hoping to get your feedback. So I hope you donât mind if I forward this message from the original thread to you.
>
> Cheers,
> Max
>
> Begin forwarded message:
>
>> From: Max Leske <maxleske(a)gmail.com>
>> Subject: Re: [Pharo-dev] Implementing lazy loading for expandable collections
>> Date: 22. September 2014 14:06:55 MESZ
>> To: Pharo Development List <pharo-dev(a)lists.pharo.org>
>>
>>
>> On 20.09.2014, at 14:27, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>>
>>> Hi Max!
>>>
>>> Thanks! This is something I wanted to push to Pharo for a long time. A simpler approach, would be to initialize the internal array to #() when initialized per default. This will provide pretty much the same benefits, and will not break the existing tools.
>>>
>>> Does this make sense to you?
>>
>> I think that would work well for standard use cases with #new. However, it wouldnât work for explicit size requests. The question of course is, how often will a collection be created with an explicit size and *still* stay empty. I guess you would know that better than me.
>>
>> I opted for the other solution because I didnât want to change the meaning of #new (which is to request a default size of 10) and because I simply assumed that even collections with explicitly requested size could stay empty.
>>
>> In terms of simplicity I like youâre idea far better of course :) It also makes a lot of changes moot that are necessary to initialize the array when required, because the array will simply be grown.
>>
>> What do your measurements say?
>>
>> Cheers,
>> Max
>>
>>>
>>> Alexandre
>>>
>>>> Le 19-09-2014 à 2:35, Max Leske <maxleske(a)gmail.com> a écrit :
>>>>
>>>> Iâve written an implementation of lazily initialized expandable collections (for OrderedCollection and subclasses only for now), inspired by Alexandreâs talk at ESUG (http://www.youtube.com/watch?v=x0YJ2dsZdKg&list=UUO-vBhaKVZf0al-ISMMPvRw) The implementation is pretty much straight forward but there are a couple of culprits I want to point out in case anybody else wants to do this:
>>>>
>>>> - my implementation requires an extra instance variable in OrderedCollection to store the requested size. This extra instance variable will break Monticello (and possibly other tools) because Monticello uses OrderedCollections to load code and the particular way it uses them makes it impossible to change the number of instance variables on OrderedCollection. Also, all .mcz files written after the change will not be loadable by images without the new instance variable (same reason).
>>>> - the above means that you have to modify the code in the image manually and save a new âbase image"
>>>> - read only messages should obviously not initialize the array. The âfirstIndexâ and âlastIndexâ variables are quite handy for that. I initialize those variables to 1 and 0 respectively which makes most things work already (e.g. #size, #isEmpty etc.).
>>>> - when trying to implement the same for HashedCollection I couldnât. The image didnât just stop working, there was no output at all on the console, not even when using a debug VM. The problem seems to be MethodDictionary, at least thatâs the only subclass of Dictionary for which adding an instance variable doesnât work.
>>>>
>>>> Iâll share some memory monitoring as soon as I have something significant (only just rolled it out).
>>>>
>>>>
>>>> Big thanks to Alex for his talk and the cool work he and his students did!
>>>>
>>>> Cheers,
>>>> Max
>>>
>>
>
Sept. 30, 2014
[pharo-project/pharo-core]
by GitHub
Branch: refs/tags/40270
Home: https://github.com/pharo-project/pharo-core
Sept. 30, 2014
[pharo-project/pharo-core] 678c48: 40270
by GitHub
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 678c4835011a768c138613df2cfb6c55d5d2ec8c
https://github.com/pharo-project/pharo-core/commit/678c4835011a768c138613df…
Author: Jenkins Build Server <board(a)pharo-project.org>
Date: 2014-09-30 (Tue, 30 Sep 2014)
Changed paths:
R Collections-Abstract.package/Collection.class/instance/private/errorNoMatch.st
A Collections-Abstract.package/Collection.class/instance/private/errorSizeMismatch.st
M Collections-Abstract.package/SequenceableCollection.class/instance/enumerating/reverseWith_do_.st
M Collections-Abstract.package/SequenceableCollection.class/instance/enumerating/select_.st
M Collections-Abstract.package/SequenceableCollection.class/instance/enumerating/select_thenCollect_.st
M Collections-Abstract.package/SequenceableCollection.class/instance/enumerating/select_thenDo_.st
M Collections-Abstract.package/SequenceableCollection.class/instance/enumerating/with_collect_.st
M Collections-Abstract.package/SequenceableCollection.class/instance/enumerating/with_do_.st
M Morphic-Widgets-Pluggable.package/PluggableTextFieldMorph.class/instance/initialization/withDropListButton.st
M Ring-Core-Containers.package/RGAbstractContainer.class/definition.st
A Ring-Core-Kernel.package/RGDefinition.class/README.md
A Ring-Core-Kernel.package/RGDefinition.class/class/annotations/authorKey.st
A Ring-Core-Kernel.package/RGDefinition.class/class/annotations/fullNameKey.st
A Ring-Core-Kernel.package/RGDefinition.class/class/annotations/timeStampKey.st
A Ring-Core-Kernel.package/RGDefinition.class/class/class initialization/named_.st
A Ring-Core-Kernel.package/RGDefinition.class/definition.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/accessing/environment.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/accessing/environment_.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/accessing/fullName.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/accessing/name.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/accessing/name_.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/accessing/rootEnvironment.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/annotations/annotationNamed_.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/annotations/annotationNamed_ifAbsentPut_.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/annotations/annotationNamed_ifAbsent_.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/annotations/annotationNamed_put_.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/annotations/annotationNames.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/annotations/annotations.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/annotations/hasAnnotationNamed_.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/annotations/hasAnnotations.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/annotations/removeAnnotationNamed_.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/converting/asRingDefinition.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isAccess.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isAssociation.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isComment.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isGlobalVariable.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isInheritance.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isInvocation.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isMethod.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isNamespace.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isOrganization.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isPackage.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isPool.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isReference.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isRingObject.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isSlice.st
A Ring-Core-Kernel.package/RGDefinition.class/instance/testing types/isVariable.st
R Ring-Core-Kernel.package/RGDefintion.class/README.md
R Ring-Core-Kernel.package/RGDefintion.class/definition.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/accessing/environment.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/accessing/environment_.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/accessing/rootEnvironment.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/annotations/annotationNamed_.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/annotations/annotationNamed_ifAbsentPut_.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/annotations/annotationNamed_ifAbsent_.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/annotations/annotationNamed_put_.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/annotations/annotationNames.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/annotations/annotations.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/annotations/hasAnnotationNamed_.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/annotations/hasAnnotations.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/annotations/removeAnnotationNamed_.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/converting/asRingDefinition.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isAccess.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isAssociation.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isComment.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isGlobalVariable.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isInheritance.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isInvocation.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isMethod.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isNamespace.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isOrganization.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isPackage.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isPool.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isReference.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isRingObject.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isSlice.st
R Ring-Core-Kernel.package/RGDefintion.class/instance/testing types/isVariable.st
M Ring-Core-Kernel.package/RGElementDefinition.class/definition.st
M Ring-Core-Kernel.package/RGGlobalDefinition.class/definition.st
R Ring-Core-Kernel.package/RGNamedDefinition.class/README.md
R Ring-Core-Kernel.package/RGNamedDefinition.class/class/annotations/authorKey.st
R Ring-Core-Kernel.package/RGNamedDefinition.class/class/annotations/fullNameKey.st
R Ring-Core-Kernel.package/RGNamedDefinition.class/class/annotations/timeStampKey.st
R Ring-Core-Kernel.package/RGNamedDefinition.class/class/class initialization/named_.st
R Ring-Core-Kernel.package/RGNamedDefinition.class/definition.st
R Ring-Core-Kernel.package/RGNamedDefinition.class/instance/accessing/fullName.st
R Ring-Core-Kernel.package/RGNamedDefinition.class/instance/accessing/name.st
R Ring-Core-Kernel.package/RGNamedDefinition.class/instance/accessing/name_.st
A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script270.st
A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40270.st
M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
Log Message:
-----------
40270
14115 Merge RGDefinition and RGNamedDefinition
https://pharo.fogbugz.com/f/cases/14115
14114 use SizeMismatch, not just #error
https://pharo.fogbugz.com/f/cases/14114
13518 Strange color and wrong positions in the Find & Replace dialog
https://pharo.fogbugz.com/f/cases/13518
http://files.pharo.org/image/40/40270.zip
Sept. 30, 2014
Re: [Pharo-dev] Context representation in current VM
by stepharo
Martin
you can add a paragraph saying that it is like that on old VM and that
now it is like described by eliot.
Stef
On 28/9/14 23:09, Martin McClure wrote:
> On 09/28/2014 12:20 PM, Eliot Miranda wrote:
>> Hi Martin,
>>
>> On Sep 28, 2014, at 1:18 AM, Martin McClure <martin(a)hand2mouse.com>
>> wrote:
>>
>>> I'm updating the exceptions chapter of Deep Into Pharo, which
>>> currently contains this text:
>>>
>>> "...some Smalltalk implementations use the native C execution stack
>>> of the virtual machine to avoid creating objects all the time.
>>> The current Pharo virtual machine does actually use full Smalltalk
>>> objects all the time; for speed, it recycles old method context
>>> objects rather than creating a new one for each message-send."
>>>
>>> Is this still true as of Pharo 4? I'd gotten the idea that this
>>> hadn't been true for a while, that the Cog VMs that Pharo is using
>>> did use a non-object stack to cache the top N contexts, only
>>> converting to actual Context objects when necessary.
>>
>> So both are true; it depends on the virtual machine. The interpreter
>> VM works as described in the existing chapter.
>
> Thanks, I'd thought that was the case.
>>
>> The Cog and Stack VMs work exactly as described in my blog post on
>> context to stack mapping. It's not really the top N contexts. The
>> stack zone, which is allocated on the native stack at startup, is
>> divided into pages, each of which can hold up to ~ 40 activations
>> (depending on stack depth, determined by #temps and nested call
>> complexity). By default there are 160 pages. That either means 160
>> pages full of activations of a single process (eg one that is deeply
>> recursive) or 1 page of up to 40 activations of 160 different
>> processes or any combination in between. ie a page can only be used
>> by a single process. When a new page is needed the oldest one is
>> emptied by ensuring all activations on the page have contexts (on the
>> heap), and updating the state of those contexts, effectively writing
>> the page to the heap in the form of contexts.
>
> Ah, I'll have to reread that blog post.
>
> The remaining question is: For the purposes of this chapter, which is
> the default VM for Pharo 4?
>
> Regards,
>
> -Martin
>
>
Sept. 30, 2014
[pharo-project/pharo-core]
by GitHub
Branch: refs/tags/40269
Home: https://github.com/pharo-project/pharo-core
Sept. 30, 2014
[pharo-project/pharo-core] 209942: 40269
by GitHub
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 20994276f5ebaf7a16734f20b4ba1e35a3a2702d
https://github.com/pharo-project/pharo-core/commit/20994276f5ebaf7a16734f20…
Author: Jenkins Build Server <board(a)pharo-project.org>
Date: 2014-09-30 (Tue, 30 Sep 2014)
Changed paths:
A Morphic-Base.package/MenuItemMorph.class/instance/accessing/enabled.st
A Morphic-Base.package/MenuItemMorph.class/instance/accessing/enabled_.st
R Morphic-Base.package/MenuItemMorph.class/instance/change reporting/ownerChanged.st
M Morphic-Base.package/MenuItemMorph.class/instance/drawing/drawOn_.st
A Morphic-Base.package/MenuItemMorph.class/instance/events/deselectTimeOut_.st
A Morphic-Base.package/MenuItemMorph.class/instance/events/mouseDown_.st
M Morphic-Base.package/MenuItemMorph.class/instance/events/mouseEnter_.st
M Morphic-Base.package/MenuItemMorph.class/instance/events/mouseUp_.st
A Morphic-Base.package/MenuItemMorph.class/instance/events/themeChanged.st
M Morphic-Base.package/MenuItemMorph.class/instance/private/subMenuMarker.st
R Morphic-Base.package/MenuItemMorph.class/instance/private/updateLayoutInDockingBar.st
R Morphic-Base.package/MenuItemMorph.class/instance/rounding/roundedCorners.st
R Morphic-Base.package/MenuItemMorph.class/instance/rounding/wantsRoundedCorners.st
M Morphic-Base.package/MenuItemMorph.class/instance/selecting/adjacentTo.st
R Morphic-Base.package/MenuItemMorph.class/instance/submorphs-accessing/noteNewOwner_.st
M Morphic-Base.package/MenuLineMorph.class/README.md
R Morphic-Base.package/MenuLineMorph.class/instance/change reporting/ownerChanged.st
M Morphic-Base.package/MenuLineMorph.class/instance/layout/minHeight.st
M Morphic-Base.package/MenuLineMorph.class/instance/layout/minWidth.st
R Morphic-Base.package/MenuLineMorph.class/instance/private/updateLayoutInDockingBar.st
R Morphic-Base.package/MenuLineMorph.class/instance/submorphs-accessing/noteNewOwner_.st
M Morphic-Base.package/ToggleMenuItemMorph.class/instance/accessing/selectionBorderStyle.st
M Morphic-Base.package/ToggleMenuItemMorph.class/instance/accessing/stringBoundsToUse.st
M Morphic-Base.package/ToggleMenuItemMorph.class/instance/drawing-private/drawSubMenuMarker_on_in_.st
M Morphic-Base.package/ToggleMenuItemMorph.class/instance/private/selectionFillStyle.st
M Morphic-Base.package/ToggleMenuItemMorph.class/instance/selecting/adjacentTo.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/README.md
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/definition.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/change reporting/ownerChanged.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/drawing/drawOn_.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/events/deselectTimeOut_.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/events/mouseDown_.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/events/mouseEnter_.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/events/mouseUp_.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/private/subMenuMarker.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/private/updateLayoutInDockingBar.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/rounding/wantsRoundedCorners.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/selecting/adjacentTo.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/submorphs-accessing/noteNewOwner_.st
A Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/submorphs-accessing/roundedCorners.st
A Morphic-Widgets-Extra.package/DockingBarMenuLineMorph.class/README.md
A Morphic-Widgets-Extra.package/DockingBarMenuLineMorph.class/definition.st
A Morphic-Widgets-Extra.package/DockingBarMenuLineMorph.class/instance/change reporting/ownerChanged.st
A Morphic-Widgets-Extra.package/DockingBarMenuLineMorph.class/instance/layout/minHeight.st
A Morphic-Widgets-Extra.package/DockingBarMenuLineMorph.class/instance/layout/minWidth.st
A Morphic-Widgets-Extra.package/DockingBarMenuLineMorph.class/instance/private/updateLayoutInDockingBar.st
A Morphic-Widgets-Extra.package/DockingBarMenuLineMorph.class/instance/submorphs-accessing/noteNewOwner_.st
A Morphic-Widgets-Extra.package/DockingBarMorph.class/class/example/example.st
A Morphic-Widgets-Extra.package/DockingBarMorph.class/class/example/exampleWithMenu.st
M Morphic-Widgets-Extra.package/DockingBarMorph.class/instance/construction/addLine.st
M Morphic-Widgets-Extra.package/DockingBarMorph.class/instance/construction/add_icon_help_subMenu_.st
M Morphic-Widgets-Extra.package/DockingBarMorph.class/instance/menu/add_font_icon_help_subMenu_.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/README.md
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/definition.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/deselectTimeOut_.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/drawOn_.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/mouseDown_.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/mouseEnter_.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/mouseUp_.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/noteNewOwner_.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/ownerChanged.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/roundedCorners.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/selectionBorderStyle.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/stringBoundsToUse.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/subMenuMarker.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/updateLayoutInDockingBar.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/wantsRoundedCorners.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/drawing-private/drawSubMenuMarker_on_in_.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/private/selectionFillStyle.st
A Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/selecting/adjacentTo.st
R Polymorph-Widgets.package/extension/MenuItemMorph/instance/deselectTimeOut_.st
R Polymorph-Widgets.package/extension/MenuItemMorph/instance/enabled.st
R Polymorph-Widgets.package/extension/MenuItemMorph/instance/enabled_.st
R Polymorph-Widgets.package/extension/MenuItemMorph/instance/mouseDown_.st
R Polymorph-Widgets.package/extension/MenuItemMorph/instance/themeChanged.st
A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script269.st
A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40269.st
M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
Log Message:
-----------
40269
14111 Handle isInDockingBar conditional logic
https://pharo.fogbugz.com/f/cases/14111
http://files.pharo.org/image/40/40269.zip
Sept. 30, 2014