September 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Ann] New Seamless version 0.9.0

by Sean P. DeNigris

Denis Kudriashov wrote >> Is that to say that the network holds them strongly? I'm curious, why? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Ann-New-Seamless-version-0-9-0-tp4914168p4914408.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 6, 2016

Re: [Pharo-dev] [Ann] New Seamless version 0.9.0

by Denis Kudriashov

2016-09-06 18:01 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Denis Kudriashov wrote > > But it could be problem if you will manage your domain objects be > > transferred as value. > > I don't understand. Does this relate to classes not being loaded in the > system? > Imaging that you have Point with format (x,y) on server and with format (x,y,z) on client. In such case there will be problems while transferring Point instances as copy (by value) between server and client. But by default most of objects are transferred by reference.

Sept. 6, 2016

Re: [Pharo-dev] [Ann] New Seamless version 0.9.0

by Denis Kudriashov

2016-09-06 18:01 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Is that to say that the network holds them strongly? yes

Sept. 6, 2016

Re: [Pharo-dev] [Ann] New Seamless version 0.9.0

by Sean P. DeNigris

Denis Kudriashov wrote > But it could be problem if you will manage your domain objects be > transferred as value. I don't understand. Does this relate to classes not being loaded in the system? Denis Kudriashov wrote > During network lifetime unused proxies and references are not collected. > It > can be performed only manually (for example when you close network and it > collected by itself or there is "network destroy" command). Is that to say that the network holds them strongly? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Ann-New-Seamless-version-0-9-0-tp4914168p4914393.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 6, 2016

Re: [Pharo-dev] finalization

by Ben Coman

Apologies. What a bogus post! I must have been really tripping.... On Tue, Sep 6, 2016 at 9:26 PM, Ben Coman <btc(a)openinworld.com> wrote: > I thought I was starting to get a grip on how finalization work. I > made this example... > > Object subclass: #MyObject > instanceVariableNames: '' > classVariableNames: '' > package: 'Play' > > MyObject>>autoRelease > ^ self class finalizationRegistry add: self > > MyObject>>finalize > Transcript crShow: 'Finalizing MyObject' > > o := MyObject new autoRelease. > o := nil. > Smalltalk garbageCollect. ==> 'Finalizing MyObject' > > So far so good. Extrapolating... I would *expect* this... > > oc := OrderedCollection new. > 10 timesRepeat: [ oc add: Libclang getClangVersion ]. > oc removeAll. > oc := nil. > Smalltalk garbageCollect. > > ...to print 'Finalizing MyObject' ten times, but it does nothing!! > Duh! I didn't send autorelease inside the timesRepeat above... Duh^2 !! that example didn't even refer to MyObject!!!!! Of course fixing those two things to get... 10 timesRepeat: [ oc add: MyObject new autoRelease. ]. works perfectly! > Such a simple example feeds my naive presumption that the system seems > broken. So could someone help me interpret this result ? Sorry for the noise. Pure PIBKAM**. Couldn't see the trees for the forest. cheers -ben **problem is between keyboard and mouse.

Sept. 6, 2016

Re: [Pharo-dev] [Ann] New Seamless version 0.9.0

by Denis Kudriashov

2016-09-06 16:37 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Denis Kudriashov wrote > > Yes, it is new implementation of remote smalltalk. Look at my blog for > > details and docs > > http://dionisiydk.blogspot.fr/2016/07/major-seamless-update.html > > Wow! This is really awesome. I love that you don't have to have the classes > loaded in the image to deal with the proxies. I've been running into a > problem lately that I have many images with overlapping domains that need > to > talk to each other. > But it could be problem if you will manage your domain objects be transferred as value. Different format of objects in such cases will be problem. > It's gotten messy because by default I use > SimplePersistence and it's easy to get into hairy situations where the data > gets unsynced. Could Seamless be appropriate for general inter-image > communication or is there a better alternative? > It is appropriate. But one important feature is absent now. It is distributed garbage collection. During network lifetime unused proxies and references are not collected. It can be performed only manually (for example when you close network and it collected by itself or there is "network destroy" command). Alternative of course is classic http services (Zinc) without any magic.

Sept. 6, 2016

Re: [Pharo-dev] [Pharo-users] [ann] pillar support in gtinspector

by Nicolai Hess

2016-08-29 21:41 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > I updated the Pillar support in GTInspector. Some of the extensions > already exist in the default Pillar #development version. If you want to > play with the full support, you can load it like this: > > Gofer new > smalltalkhubUser: 'Moose' project: 'PetitParser'; > package: 'PetitAnalyzer'; > package: 'PetitIndent'; > package: 'PetitIslands'; > smalltalkhubUser: 'Moose' project: 'GToolkit'; > package: 'GT-InspectorExtensions-Pillar'; > load > > Then you can just inspect a book folder and you get this: > > > I did not integrate this in the main Pillar yet because this is an older > implementation based on a limited island parser. As now Pillar has a full > parser based on PetitParser, the next step is to move the highlighting > logic to use this parser instead of the island parser. From my > measurements, the speed of the two parsers is about the same, so from a > user perspective there will be not much changes. > > It pains me that we are editing Pillar in outside tools, and now we should > no longer have to do that. Of course, this is not the most ideal tool > support for Pillar but I think it is a reasonable start. > > Cheers, > Doru > nice! I just played a bit with the code to apply larger different font sizes for the headings and use the code styler for inlined code ("=="). Maybe we should use a different code styler or add a way to instruct the styler to ignore unknown classes or uknown selectors :) > > > -- > www.tudorgirba.com > www.feenk.com > > "Problem solving should be focused on describing > the problem in a way that makes the solution obvious." > > > > > >

Sept. 6, 2016

Re: [Pharo-dev] Copying/Duplicating a class also duplicates pool dictionaries

by Ben Coman

On Tue, Sep 6, 2016 at 9:49 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2016-09-06 15:39 GMT+02:00 Ben Coman <btc(a)openinworld.com>: >> >> Just bumped into a curious thing. I went copy a class with a pool >> dictionary... >> >> FFIExternalStructure subclass: #CXString >> instanceVariableNames: '' >> classVariableNames: '' >> poolDictionaries: 'CXStringFlag' >> package: 'Libclang' >> >> and it asked me for the new name, to which I dutifully entered 'CXString2' >> after which I was asked... >> "CXString2Flag does not exist. Do you want it automatically created?" >> >> Choosing "No" fails the CXString copy since CXString2Flag does not exist. >> Choosing "Yes" produces... >> >> FFIExternalStructure subclass: #CXString2 >> instanceVariableNames: '' >> classVariableNames: '' >> poolDictionaries: 'CXString2Flag' >> package: 'Libclang' >> >> So I'm curious what the reasoning is for making a parallel copy of the >> pool dictionary? >> >> And btw, CXString2Flag gets created in the "Unclassified" package and >> fails to copy the methods from the original. >> >> cheers -ben > > > > > What image version ? Moose 6.0, Pharo 50761. sorry I didn't check in latest already. I first wanted to understand what the expected behaviour was. > > We had an issue for a similar case (the class /instance variable names were > copied *and* renamed too) > > 18957 Class copy should not change the name of the instance variables > > This was fixed n 60189 > > (actually, with this change, the pool dictionary definition is just *not* > copied but empty, hm, but I think this is better > than creating a new with the changed name). Tested in 60205, it does behave better, but I added a new issue with this additional fix attached... https://pharo.fogbugz.com/default.asp?19050 However are there any other class definition features (like slots) that should be considered? I don't know what classes use slots that could be tested. cheers -ben > >

Sept. 6, 2016

[pharo-project/pharo-core]

by GitHub

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

Sept. 6, 2016

[pharo-project/pharo-core] 017262: 60206

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 0172620e6d099ec55180846504025c1003fdd69f https://github.com/pharo-project/pharo-core/commit/0172620e6d099ec551808465… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-06 (Tue, 06 Sep 2016) Changed paths: R Collections-Tests.package/StringTest.class/instance/tests - converting/testZipped.st A Compression-Tests.package/ZipWriteStreamTests.class/instance/tests/testZipped.st A Kernel-Tests.package/ProcessTest.class/instance/testing/testInjectingExceptionHandlerFromProcessItself.st A Kernel-Tests.package/ProcessTest.class/instance/testing/testInjectingExceptionHandlerIntoNotRunningProcess.st A Kernel-Tests.package/ProcessTest.class/instance/testing/testInjectingExceptionHandlerIntoRunningProcess.st A Kernel-Tests.package/ProcessTest.class/instance/testing/testInjectingMultipleExceptionHandlersIntoNotRunningProcess.st A Kernel-Tests.package/ProcessTest.class/instance/testing/testInjectingMultipleExceptionHandlersIntoRunningProcess.st A Kernel.package/Process.class/instance/signaling/on_do_.st A Nautilus-Tests.package/NautilusUtilsTest.class/instance/tests/testAsTestMethod.st M Nautilus-Tests.package/NautilusUtilsTest.class/instance/tests/testCorrespondingTestCase.st M Nautilus-Tests.package/NautilusUtilsTest.class/instance/tests/testCorrespondingTestMethod.st M Nautilus-Tests.package/NautilusUtilsTest.class/instance/tests/testCorrespondingTestedMethods.st A Nautilus-Tests.package/NautilusUtilsTest.class/instance/tests/testNormalizedSelectorForComparison.st R Nautilus-Tests.package/NautilusUtilsTest.class/instance/tests/testTransformSelectorForComparison.st M Nautilus.package/AbstractNautilusUI.class/instance/icon caches/removeFromMethodsIconsCache_.st M Nautilus.package/AbstractNautilusUI.class/instance/icon/packageIconFor_.st M Nautilus.package/MethodWidget.class/class/menu/elementsMenu_.st M Nautilus.package/MethodWidget.class/instance/icon/methodIconFor_.st M Nautilus.package/MethodWithCorrespondingTestAction.class/instance/order/isActionHandled.st M Nautilus.package/NautilusUI.class/class/menus behavior/runTestForAMethod_notifying_.st M Nautilus.package/NautilusUI.class/instance/debugging actions/debugTest.st A NautilusCommon.package/NautilusUtils.class/class/utilities/asTestMethod_.st M NautilusCommon.package/NautilusUtils.class/class/utilities/correspondingTestMethodOf_.st M NautilusCommon.package/NautilusUtils.class/class/utilities/correspondingTestedMethodsOf_.st A NautilusCommon.package/extension/CompiledMethod/instance/asTestMethod.st M NautilusCommon.package/extension/CompiledMethod/instance/correspondingTestMethod.st M NautilusCommon.package/extension/RGClassDescriptionDefinition/instance/correspondingTestCase.st A NautilusCommon.package/extension/RGMethodDefinition/instance/asTestMethod.st M NautilusCommon.package/extension/RGMethodDefinition/instance/correspondingTestMethod.st A NautilusCommon.package/extension/String/instance/normalizedSelectorForComparison.st R NautilusCommon.package/extension/String/instance/transformSelectorForComparison.st M SUnit-Core.package/TestExecutionEnvironment.class/instance/controlling/watchDogLoopFor_.st A SUnit-Tests.package/SUnitTest.class/instance/testing/testShouldIgnoreTimeLimitWhenTestProcessIsSuspended.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60205.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60206.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60205.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60206.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60206 19048 move testZipped to Compression-Tests https://pharo.fogbugz.com/f/cases/19048 19046 SUnit watch dog should not signal error when test environment is not active like during debugger https://pharo.fogbugz.com/f/cases/19046 19028 Process ondo method to inject default exception handlers https://pharo.fogbugz.com/f/cases/19028 18974 A Nautilus fix to support class method tests https://pharo.fogbugz.com/f/cases/18974 http://files.pharo.org/image/60/60206.zip

Sept. 6, 2016