- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50690 Home: https://github.com/pharo-project/pharo-core

April 14, 2016

[pharo-project/pharo-core] db8773: 50690

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: db8773cc6c5bd4145e72f220ac240b1df2a533eb https://github.com/pharo-project/pharo-core/commit/db8773cc6c5bd4145e72f220… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-14 (Thu, 14 Apr 2016) Changed paths: M Morphic-Core.package/Morph.class/instance/updating/addDependent_.st M Nautilus.package/AbstractNautilusUI.class/instance/build ui text/buildNewCodeSourceAreaRubric.st M Nautilus.package/AbstractNautilusUI.class/instance/build ui text/buildNewCommentText.st M Nautilus.package/NautilusAnnotationDisplayer.class/instance/submorphs-accessing/noteNewOwner_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50689.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50690.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50689.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50690.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/TreeModel.class/instance/initialization/registerEvents.st M Spec-MorphicAdapters.package/extension/PluggableTextMorph/instance/registerScrollChanges_.st M Tool-Diff.package/DiffMorph.class/instance/initialization/initialize.st M Tool-Finder.package/FinderUI.class/instance/items creation/buildSourceTextArea.st Log Message: ----------- 50690 18003 multiple usage in the weak subscriptions to the local announcers in the system https://pharo.fogbugz.com/f/cases/18003 http://files.pharo.org/image/50/50690.zip

April 14, 2016

How to hide particular methods in debugger stack widgect

by Denis Kudriashov

Hi. I remember that it was possible to filter methods on stack debugger view. What pragma I should use?

April 14, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] 70e814: 50689

by Marcus Denker

> > Log Message: > ----------- > 50689 > Moose This is 18001 GToolkit version 3.19 https://pharo.fogbugz.com/f/cases/18001 > > http://files.pharo.org/image/50/50689.zip > >

April 14, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50689 Home: https://github.com/pharo-project/pharo-core

April 14, 2016

[pharo-project/pharo-core] 70e814: 50689

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 70e81419758cf2b62d4a8dee9e1ff25cc29013f8 https://github.com/pharo-project/pharo-core/commit/70e81419758cf2b62d4a8dee… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-14 (Thu, 14 Apr 2016) Changed paths: M ConfigurationOfGTDebugger.package/ConfigurationOfGTDebugger.class/instance/symbolic versions/stable_.st A ConfigurationOfGTDebugger.package/ConfigurationOfGTDebugger.class/instance/versions/version27_.st M ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version38_.st M ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version38_.st M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic versions/stable_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version28_.st M ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/versions/version319_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version411_.st M GT-Inspector.package/GTDummyExamplesWithAfter.class/class/as yet unclassified/a_.st M GT-Inspector.package/GTDummyExamplesWithAfter.class/class/as yet unclassified/b_.st M GT-Inspector.package/GTDummyExamplesWithAfter.class/class/as yet unclassified/c.st A GT-Inspector.package/GTDummyExamplesWithAfter2.class/README.md A GT-Inspector.package/GTDummyExamplesWithAfter2.class/class/as yet unclassified/afterB_b_b_.st A GT-Inspector.package/GTDummyExamplesWithAfter2.class/class/as yet unclassified/afterC_c_c_.st A GT-Inspector.package/GTDummyExamplesWithAfter2.class/class/as yet unclassified/afterD_d_d_.st A GT-Inspector.package/GTDummyExamplesWithAfter2.class/class/as yet unclassified/b_.st A GT-Inspector.package/GTDummyExamplesWithAfter2.class/class/as yet unclassified/c_.st A GT-Inspector.package/GTDummyExamplesWithAfter2.class/class/as yet unclassified/d.st A GT-Inspector.package/GTDummyExamplesWithAfter2.class/definition.st A GT-Inspector.package/GTDummyExamplesWithAfter2WithExceptions.class/README.md A GT-Inspector.package/GTDummyExamplesWithAfter2WithExceptions.class/class/as yet unclassified/afterB_b_b_.st A GT-Inspector.package/GTDummyExamplesWithAfter2WithExceptions.class/class/as yet unclassified/afterC_c_c_.st A GT-Inspector.package/GTDummyExamplesWithAfter2WithExceptions.class/class/as yet unclassified/afterD_d_d_.st A GT-Inspector.package/GTDummyExamplesWithAfter2WithExceptions.class/class/as yet unclassified/b2_.st A GT-Inspector.package/GTDummyExamplesWithAfter2WithExceptions.class/class/as yet unclassified/b3_.st A GT-Inspector.package/GTDummyExamplesWithAfter2WithExceptions.class/class/as yet unclassified/c_.st A GT-Inspector.package/GTDummyExamplesWithAfter2WithExceptions.class/class/as yet unclassified/d.st A GT-Inspector.package/GTDummyExamplesWithAfter2WithExceptions.class/definition.st M GT-Inspector.package/GTDummyExamplesWithAfterFinish.class/class/as yet unclassified/a_.st M GT-Inspector.package/GTDummyExamplesWithAfterFinish.class/class/as yet unclassified/b_.st M GT-Inspector.package/GTDummyExamplesWithAfterFinish.class/class/as yet unclassified/c.st A GT-Inspector.package/GTExample.class/instance/pragma-selectors/afterClass_selector_arguments_.st A GT-Inspector.package/GTExample.class/instance/pragma-selectors/afterFinishClass_selector_arguments_.st A GT-Inspector.package/GTExample.class/instance/pragma-selectors/after_arguments_.st M GT-Inspector.package/GTExample.class/instance/private/methodForClassNamed_selector_.st M GT-Inspector.package/GTExample.class/instance/private/methodForProvider_selector_.st A GT-Inspector.package/GTExample.class/instance/public/afterArguments.st M GT-Inspector.package/GTExample.class/instance/public/method.st A GT-Inspector.package/GTExample.class/instance/public/providerClass.st A GT-Inspector.package/GTExample.class/instance/testing/hasValidAfterArguments.st M GT-Inspector.package/GTExampleEvaluator.class/README.md M GT-Inspector.package/GTExampleEvaluator.class/definition.st M GT-Inspector.package/GTExampleEvaluator.class/instance/primitives/primitiveProcessExampleAfterFinish_.st M GT-Inspector.package/GTExampleEvaluator.class/instance/primitives/primitiveProcessExampleAfter_.st M GT-Inspector.package/GTExampleEvaluator.class/instance/primitives/primitiveProcessExample_withArguments_.st M GT-Inspector.package/GTExampleEvaluator.class/instance/private/process_withArguments_.st A GT-Inspector.package/GTExampleEvaluator.class/instance/private/withLinkContextFor_do_.st A GT-Inspector.package/GTExampleLinkContext.class/README.md A GT-Inspector.package/GTExampleLinkContext.class/definition.st A GT-Inspector.package/GTExampleLinkContext.class/instance/accessing/example.st A GT-Inspector.package/GTExampleLinkContext.class/instance/accessing/example_.st A GT-Inspector.package/GTExampleLinkContext.class/instance/private/install.st A GT-Inspector.package/GTExampleLinkContext.class/instance/private/onLinkNode_arguments_.st A GT-Inspector.package/GTExampleLinkContext.class/instance/private/onLinkNode_at_put_.st A GT-Inspector.package/GTExampleLinkContext.class/instance/private/uninstall.st A GT-Inspector.package/GTExampleLinkContext.class/instance/private/withLinksDo_.st A GT-Inspector.package/GTExampleLinkContext.class/instance/public/arguments.st A GT-Inspector.package/GTExampleLinkContext.class/instance/public/do_.st A GT-Inspector.package/GTExampleLinkContext.class/instance/testing/hasLinks.st M GT-Inspector.package/GTExampleMethod.class/README.md M GT-Inspector.package/GTExampleMethod.class/definition.st M GT-Inspector.package/GTExampleMethod.class/instance/accessing/provider.st R GT-Inspector.package/GTExampleMethod.class/instance/accessing/providerName_.st M GT-Inspector.package/GTExampleMethod.class/instance/accessing/provider_.st M GT-Inspector.package/GTExampleMethod.class/instance/testing/exists.st A GT-Inspector.package/GTExampleMethod.class/instance/testing/hasValidArguments.st A GT-Inspector.package/GTExampleProviderMethod.class/README.md A GT-Inspector.package/GTExampleProviderMethod.class/definition.st A GT-Inspector.package/GTExampleProviderMethod.class/instance/accessing-defaults/defaultProvider.st A GT-Inspector.package/GTExampleProviderMethod.class/instance/accessing/arguments.st A GT-Inspector.package/GTExampleProviderMethod.class/instance/accessing/arguments_.st A GT-Inspector.package/GTExampleProviderMethod.class/instance/accessing/provider.st A GT-Inspector.package/GTExampleProviderMethod.class/instance/accessing/providerName_.st A GT-Inspector.package/GTExampleProviderMethod.class/instance/accessing/provider_.st A GT-Inspector.package/GTExampleProviderMethod.class/instance/testing/hasValidArguments.st M GT-Inspector.package/GTExampleResult.class/instance/ui/gtDisplayOn_.st R GT-Inspector.package/GTExampleResult.class/instance/ui/gtDisplaySummaryOn_.st M GT-Inspector.package/GTExampleTestCase.class/instance/private/runExample_fromContainer_.st A GT-Inspector.package/GTExampleUnexpectedExceptionRaised.class/instance/ui/gtDisplayOn_.st M GT-Inspector.package/GTProtoObjectVariablesBrowser.class/instance/private building/variableValuePairsFor_.st A GT-Playground.package/extension/GLMSystemWindow/instance/model_.st M GT-SpotterExtensions-Core.package/extension/GTSpotter/instance/spotterForMetacelloConfigurationsFor_.st M Glamour-Morphic-Renderer.package/GLMMorphicActionRenderer.class/instance/rendering/render_.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoMethodRenderer.class/instance/rendering/morph.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoScriptRenderer.class/instance/rendering/morph.st A Glamour-Morphic-Renderer.package/GLMPluggableButtonMorph.class/README.md A Glamour-Morphic-Renderer.package/GLMPluggableButtonMorph.class/definition.st A Glamour-Morphic-Renderer.package/GLMPluggableButtonMorph.class/instance/as yet unclassified/model_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50688.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50689.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50688.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50689.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50689 Moose http://files.pharo.org/image/50/50689.zip

April 14, 2016

[pharo-project/pharo-core] b582ad: 50688

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: b582ad57dd8926bd3130f3b26170e2d95a0d6f09 https://github.com/pharo-project/pharo-core/commit/b582ad57dd8926bd3130f3b2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-14 (Thu, 14 Apr 2016) Changed paths: M Athens-Cairo.package/AthensCairoMatrix.class/instance/transformations/transform_.st M Athens-Cairo.package/AthensCairoTransform.class/instance/vector-transform/transform_.st M ConfigurationOfAthens.package/ConfigurationOfAthens.class/instance/symbolic versions/stable_.st A ConfigurationOfAthens.package/ConfigurationOfAthens.class/instance/versions/version393_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50687.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50688.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50687.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50688.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50688 17998 Update Athens to latest https://pharo.fogbugz.com/f/cases/17998 http://files.pharo.org/image/50/50688.zip

April 14, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50688 Home: https://github.com/pharo-project/pharo-core

April 14, 2016

Re: [Pharo-dev] [Pharo-users] STON materialization corrupts a dictionary if the keys are references

by Sven Van Caekenberghe

Thanks everybody for the feedback/discussions, it helped a lot. I made a new version that is simpler and better, as well as more correct. === Name: STON-Core-SvenVanCaekenberghe.72 Author: SvenVanCaekenberghe Time: 14 April 2016, 2:17:40.799554 pm UUID: 80f809ee-2693-47c7-adf5-d56a9647d78c Ancestors: STON-Core-SvenVanCaekenberghe.71 New, better, more correct implementation of Dictionary/Set rehashing after reference resolution made them potentially unhealthy. See the new tests #testDictionaryWithIndirectReferenceKeys and #testSetWithIndirectReferenceElements for example cases that were not covered by the previous optimization. During resolution of references we count the number of unresolved references backwards so that we know when #stonProcessSubObjects: did actually resolve a reference (possible deep down). If that is the case we call a new hook called #stonPostReferenceResolution that does nothing by default. For Dictionary and Set #stonPostReferenceResolution is implemented as self isHealthy ifFalse: [ self rehash ] Now, rehashing is only done when absolutely necesary (this is crucial for performance). We even avoid the possibly expensive #isHealthy check when no references were actually resolved and hence no hashing could possibly change. === Name: STON-Tests-SvenVanCaekenberghe.64 Author: SvenVanCaekenberghe Time: 14 April 2016, 2:17:59.88328 pm UUID: 1401dc66-e503-4da1-bc7c-30dd0a4afa06 Ancestors: STON-Tests-SvenVanCaekenberghe.63 === Sven > On 06 Apr 2016, at 17:58, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > Not really about modifying during iteration, if an object you try to remove: is in the wrong slot, you'll most likely get a CannotBeFound error. > > Which you can work around by iterating indexes and nilling directly, doing so in reverse merely minimizes the amount of work needed to potentially fill the slot when it is still empty after re-adding. > (Maintain index of next nil slot as well, test backwards from that, and you should get away with the minimal amount of work required... Just need to ensure it's still nil, and not the slot removed object was put in) > > Needless to say, it'd probably end up pretty hairy, and still have worse > worse-case perf* than rehash, though average-case would probably be much better. > > Cheers, > Henry > > * worst-case performance in linearly hashed tables is *much* worse for remove than add, due to the potential fixups needed when the set is dense... Consider at:ifAbsent: perf experienced for missing entries in default sized Unicode tables with hash at start of longest non-nil sequence of slots, and multiply by 100 >> On 6. apr. 2016, at 21.07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Yeah, I just realised that iterating and changing a dictionary or set at the same time won't work ;-) >> >>> On 06 Apr 2016, at 16:01, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>> >>> If you are iterating over a Set with incorrectly placed objects, remove: calls aren't going to do you much good ;) >>> Not to mention, even nilling the slot directly, then add:'ing, still means you have to scan subsequent entries up to the next empty slot for potentially better placement, if the object ended up being added elsewhere. >>> (IOW, if you're gonna do it, better iterate in reverse) >>> >>> Cheers, >>> Henry >>> >>>> On 06 Apr 2016, at 3:46 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> >>>>> On 06 Apr 2016, at 15:34, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>>>> >>>>> >>>>> >>>>> 2016-04-06 15:25 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>>> Hi Nicolai, >>>>> >>>>>> On 06 Apr 2016, at 14:56, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>>>>> >>>>>> >>>>>> >>>>>> 2016-04-06 14:27 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>>>> Fix for review: >>>>>> >>>>>> === >>>>>> Name: STON-Core-SvenVanCaekenberghe.71 >>>>>> Author: SvenVanCaekenberghe >>>>>> Time: 6 April 2016, 2:22:24.782251 pm >>>>>> UUID: 64b8b741-365e-41fe-aa98-565e33ca5d24 >>>>>> Ancestors: STON-Core-SvenVanCaekenberghe.70 >>>>>> >>>>>> Fix a bug where STONReferences occurring as keys in Dictionaries or elements in Sets caused those to be unhealthy after materialization. Thx to Peter UhnÃ¡k for reporting this issue. >>>>>> >>>>>> Add 3 new unit tests to STONReaderTests >>>>>> >>>>>> #testDictionaryWithReferenceKeys >>>>>> #testSetWithReferenceElements >>>>>> #testDeepStructure >>>>>> >>>>>> Fix Details >>>>>> >>>>>> change the implementation of STONReader>>#processSubObjectsOf: from iterative to recursive (see version 39 of 29 November 2012, this might be a functional regression, see #testDeepStructure; cleanup of stack instance variable for later) so that #stonProcessSubObjects: can be overwritten with code being executed before or after full reference resolution >>>>>> >>>>>> imho, recursion stack depth will be equal during both writing and reading, and should be acceptable. >>>>>> >>>>>> overwrite #stonProcessSubObjects: in Dictionary and Set to #rehash at the end, but only when needed (minimal optimalization, see Dictionary>>#containsStonReferenceAsKey and Set>>#containsStonReference) >>>>>> === >>>>>> Name: STON-Tests-SvenVanCaekenberghe.63 >>>>>> Author: SvenVanCaekenberghe >>>>>> Time: 6 April 2016, 2:22:45.01986 pm >>>>>> UUID: 0beb2322-b81a-46ee-a0e2-6648a808774a >>>>>> Ancestors: STON-Tests-SvenVanCaekenberghe.62 >>>>>> >>>>>> (idem) >>>>>> === >>>>> >>>>> Thanks for looking at the code. >>>>> >>>>>> Hi Sven, >>>>>> instead of rehashing the dictionary for every ston reference, >>>>> >>>>> (It rehashes only once after resolving all references) >>>>> >>>>> Ah, of course. I thought this would be called for every ston reference used as key. >>>>> >>>>> >>>>> >>>>>> wouldn't it work to remove and readd the value after processing the subobject: >>>>>> >>>>>> Dictionary>>#stonProcessSubObjects: block >>>>>> self keys do:[:key | >>>>>> |value| >>>>>> value := block value:(self removeKey: key ifAbsent:[ nil]). >>>>>> self at: (block value: key) put: value]. >>>>> >>>>> Interesting idea. I have to think about that approach. >>>>> >>>>> Now, Object>>#stonProcessSubObjects: is very general and looks at named and indexed instance variables. But this probably could be replaced by something more high level and specific I guess. >>>>> >>>>> Adding and removing each key/value has a cost too. I try to make the simplest case very efficient and only pay a price when really needed. Anyway, time for some calculations. >>>>> >>>>> ok, yes running over all keys isn't better than rehashing :-) >>>> >>>> Still, your idea might be better than you would expect: >>>> >>>> Now, there is 1 (partial) iteration to do the check before, 2 iterations over the keys and values arrays, then an optional full rehash (which also reallocates and thus generates garbage). >>>> >>>> Your idea does only 1 iteration over keys, with remove and add (which also happens more efficiently on the arrays above), no check before, no rehash, probably no garbage generation at all in any case. >>>> >>>> Like I said, I have to study it (especially the cost of remove/add, maybe that can be optimised a bit as well). >>>> >>>>> Thanks again for the suggestion ! >>>>> >>>>> Sven >>>>> >>>>>>> On 06 Apr 2016, at 14:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>>>> >>>>>>> https://pharo.fogbugz.com/f/cases/17946/STON-materializes-unhealthy-Diction… >>>>>>> >>>>>>> fix coming >>>>>>> >>>>>>>>> On 05 Apr 2016, at 13:11, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> On 05 Apr 2016, at 13:02, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> 2016-04-05 12:32 GMT+02:00 Cyril Ferlicot Delbecque <cyril.ferlicot(a)gmail.com>: >>>>>>>>> >>>>>>>>> >>>>>>>>>> On 05/04/2016 12:09, Sven Van Caekenberghe wrote: >>>>>>>>>> >>>>>>>>>> Like I said, it is a hashing issue, sometimes it will be correct by accident. >>>>>>>>>> >>>>>>>>>> I hope you did not have to much trouble with this bug, I guess it must have been hard to chase. >>>>>>>>>> >>>>>>>>>> Is it urgent ? >>>>>>>>>> >>>>>>>>>> I probably can give you a quick fix, but I would like to think a bit more about this, since rehashing each materialised dictionary seems expensive. >>>>>>>>> >>>>>>>>> Hi Sven, >>>>>>>>> >>>>>>>>> I got the same kind of problem in a personal application. >>>>>>>>> >>>>>>>>> I use Sets that I serialize and I had a lot of trouble because sometimes >>>>>>>>> some action had strange behaviours. >>>>>>>>> >>>>>>>>> For example in a set with element `aSet remove: aSet anyOne` raised 'XXX >>>>>>>>> not found in aSet'. >>>>>>>>> >>>>>>>>> I am glad to hear that it is a Ston issue and not me that used sets in a >>>>>>>>> bad way :) >>>>>>>>> >>>>>>>>> For me too it is not urgent since I have a not of university work for >>>>>>>>> the moment. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> How are hashed collections created/filled during ston-parsing ? >>>>>>>>> If the position in a hashed collection is created by a ston-reference, that is later replaced by the "real" object, >>>>>>>>> the index in the dictionary (or other hashed collections) may be wrong. >>>>>>>> >>>>>>>> Yes, that is indeed it, Nicolai. >>>>>>>> >>>>>>>> But I would like to try to minimise the rehashing as it seems expensive. But first I need a more reliable failure. >>>>>>>> >>>>>>>>> -- >>>>>>>>> Cyril Ferlicot >>>>>>>>> >>>>>>>>> http://www.synectique.eu >>>>>>>>> >>>>>>>>> 165 Avenue Bretagne >>>>>>>>> Lille 59000 France >> >> >

April 14, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40627 Home: https://github.com/pharo-project/pharo-core

April 14, 2016