- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Parsing Pharo syntax to C/C++

by Frank Shearar

On 20 September 2014 08:45, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > A > Le 20 sept. 2014 03:27, "Alain Rastoul" <alf.mmm.cat(a)gmail.com> a Ã©crit : > > >> >> Le 20/09/2014 02:33, phil(a)highoctane.be a Ã©crit : >> >> >>> We'll prevail! >>> >>> What we also need to do is to showcase the Smalltalk workflow and how >>> nice it is. >>> >>> We cannot gain mindshare by technical prowess only. >>> >>> Phil >> >> >> I totally agree with you, >> but I think that those technical advances are vital in current technology >> trends (saas, cloud, server side dev) and progress in this field is >> important. >> >> Despite the fact I think that Smalltalk still has an advance in object >> oriented systems/development, and offers a different perception it is hard >> to get the point about object system with people who are formatted by the >> hype or by their experience. Discussing with collegues about some smalltalk >> concepts is always interesting :) >> >> > I am facing quite some people who are in the FP bandwagon and wonder how to > bridge with their views. Like classes are just functions etc. The article that convinced me that objects are higher order functions (that close over a set of variables) is here: http://letoverlambda.com/index.cl/guest/chap2.html The meat of the article (as far as class/object/function correspondences goes) starts at "Let over Lambda". frank > Phil

Sept. 20, 2014

[pharo-project/pharo-core] fbbc9b: 40239

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: fbbc9b857aaf65e2d0b2fcaa17a7b50061fffca6 https://github.com/pharo-project/pharo-core/commit/fbbc9b857aaf65e2d0b2fcaa… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-20 (Sat, 20 Sep 2014) Changed paths: A Deprecated40.package/extension/SystemAnnouncement/class/fromInternal_.st M Kernel.package/CompiledMethod.class/instance/accessing/origin.st M Nautilus.package/AbstractNautilusUI.class/instance/private/runTestsOfClass_notifying_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script239.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40239.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R System-Announcements.package/SystemAnnouncement.class/class/instance creation/fromInternal_.st Log Message: ----------- 40239 10572 Locking image with test icons (Glorp example) https://pharo.fogbugz.com/f/cases/10572 13843 MOPTraitTes>>#testOrigin failing https://pharo.fogbugz.com/f/cases/13843 14046 Deprecate SystemAnnouncement(class)>>fromInternal: https://pharo.fogbugz.com/f/cases/14046 http://files.pharo.org/image/40/40239.zip

Sept. 20, 2014

[pharo-project/pharo-core]

by GitHub

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

Sept. 20, 2014

Re: [Pharo-dev] Parsing Pharo syntax to C/C++

by phil＠highoctane.be

A Le 20 sept. 2014 03:27, "Alain Rastoul" <alf.mmm.cat(a)gmail.com> a Ã©crit : > > Le 20/09/2014 02:33, phil(a)highoctane.be a Ã©crit : > > >> We'll prevail! >> >> What we also need to do is to showcase the Smalltalk workflow and how >> nice it is. >> >> We cannot gain mindshare by technical prowess only. >> >> Phil > > > I totally agree with you, > but I think that those technical advances are vital in current technology trends (saas, cloud, server side dev) and progress in this field is important. > > Despite the fact I think that Smalltalk still has an advance in object oriented systems/development, and offers a different perception it is hard to get the point about object system with people who are formatted by the hype or by their experience. Discussing with collegues about some smalltalk concepts is always interesting :) > > I am facing quite some people who are in the FP bandwagon and wonder how to bridge with their views. Like classes are just functions etc. Phil

Sept. 20, 2014

[pharo-project/pharo-core] 9a993b: 40238

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 9a993b9ced41f08d98336977d877e0d4c71ba813 https://github.com/pharo-project/pharo-core/commit/9a993b9ced41f08d98336977… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-20 (Sat, 20 Sep 2014) Changed paths: M Morphic-Base.package/extension/PasteUpMorph/instance/makeAScreenshot.st M NativeBoost-Win32.package/NativeBoostWin32.class/instance/accessing/stackAlignment.st R Nautilus.package/AbstractNautilusUITest.class/README.md R Nautilus.package/AbstractNautilusUITest.class/definition.st R Nautilus.package/AbstractNautilusUITest.class/instance/initialization/setUp.st R Nautilus.package/AbstractNautilusUITest.class/instance/tests/testSortClassesInCachedHierarchyB.st R Nautilus.package/NautilusTest.class/README.md R Nautilus.package/NautilusTest.class/definition.st R Nautilus.package/NautilusTest.class/instance/running/setUp.st R Nautilus.package/NautilusTest.class/instance/running/tearDown.st R Nautilus.package/NautilusTest.class/instance/tests/testCorrespondingMethods.st R Nautilus.package/NautilusTest.class/instance/tests/testCorrespondingTestClass.st R Nautilus.package/NautilusTest.class/instance/tests/testCorrespondingTestMethod.st R Nautilus.package/NautilusTest.class/instance/tests/testSelectedCategory.st R Nautilus.package/NautilusTest.class/instance/tests/testSelectedClass.st R Nautilus.package/NautilusTest.class/instance/tests/testSelectedMethod.st R Nautilus.package/NautilusUITest.class/README.md R Nautilus.package/NautilusUITest.class/definition.st R Nautilus.package/NautilusUITest.class/instance/initialization/setUp.st R Nautilus.package/NautilusUITest.class/instance/initialization/tearDown.st R Nautilus.package/NautilusUITest.class/instance/tests/testBuildTestSelectorFor.st R Nautilus.package/SortHierarchicallyTests.class/README.md R Nautilus.package/SortHierarchicallyTests.class/definition.st R Nautilus.package/SortHierarchicallyTests.class/instance/private/asNodes_.st R Nautilus.package/SortHierarchicallyTests.class/instance/private/nodes_shouldBe_.st R Nautilus.package/SortHierarchicallyTests.class/instance/private/sortByNameSize_.st R Nautilus.package/SortHierarchicallyTests.class/instance/setup/setUp.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testArchivesClassesReversed.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testArchivesClassesUnchanged.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testArchivesClassesUnordered.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testCompleteTreeReversed.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testCompleteTreeUnchanged.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testCompleteTreeUnordered.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testOneClass.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testPartialTreeReversed.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testPartialTreeUnchanged.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testPartialTreeUnsorted.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testUnrelatedClassesReversed.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testUnrelatedClassesUnchanged.st R Nautilus.package/SortHierarchicallyTests.class/instance/tests/testUnrelatedClassesUnsorted.st A NautilusTests.package/AbstractNautilusUITest.class/README.md A NautilusTests.package/AbstractNautilusUITest.class/definition.st A NautilusTests.package/AbstractNautilusUITest.class/instance/initialization/setUp.st A NautilusTests.package/AbstractNautilusUITest.class/instance/tests/testSortClassesInCachedHierarchyB.st A NautilusTests.package/NautilusTest.class/README.md A NautilusTests.package/NautilusTest.class/definition.st A NautilusTests.package/NautilusTest.class/instance/running/setUp.st A NautilusTests.package/NautilusTest.class/instance/running/tearDown.st A NautilusTests.package/NautilusTest.class/instance/tests/testCorrespondingMethods.st A NautilusTests.package/NautilusTest.class/instance/tests/testCorrespondingTestClass.st A NautilusTests.package/NautilusTest.class/instance/tests/testCorrespondingTestMethod.st A NautilusTests.package/NautilusTest.class/instance/tests/testSelectedCategory.st A NautilusTests.package/NautilusTest.class/instance/tests/testSelectedClass.st A NautilusTests.package/NautilusTest.class/instance/tests/testSelectedMethod.st A NautilusTests.package/NautilusUITest.class/README.md A NautilusTests.package/NautilusUITest.class/definition.st A NautilusTests.package/NautilusUITest.class/instance/initialization/setUp.st A NautilusTests.package/NautilusUITest.class/instance/initialization/tearDown.st A NautilusTests.package/NautilusUITest.class/instance/tests/testBuildTestSelectorFor.st A NautilusTests.package/SortHierarchicallyTests.class/README.md A NautilusTests.package/SortHierarchicallyTests.class/definition.st A NautilusTests.package/SortHierarchicallyTests.class/instance/private/asNodes_.st A NautilusTests.package/SortHierarchicallyTests.class/instance/private/nodes_shouldBe_.st A NautilusTests.package/SortHierarchicallyTests.class/instance/private/sortByNameSize_.st A NautilusTests.package/SortHierarchicallyTests.class/instance/setup/setUp.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testArchivesClassesReversed.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testArchivesClassesUnchanged.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testArchivesClassesUnordered.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testCompleteTreeReversed.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testCompleteTreeUnchanged.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testCompleteTreeUnordered.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testOneClass.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testPartialTreeReversed.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testPartialTreeUnchanged.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testPartialTreeUnsorted.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testUnrelatedClassesReversed.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testUnrelatedClassesUnchanged.st A NautilusTests.package/SortHierarchicallyTests.class/instance/tests/testUnrelatedClassesUnsorted.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script238.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40238.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40238 14044 Selfies shot with Pharo should give visual feedback https://pharo.fogbugz.com/f/cases/14044 14008 Tests from Nautilus-Tests need to be moved to a nautilus test package https://pharo.fogbugz.com/f/cases/14008 13949 stackAlignment on windows should be 16 https://pharo.fogbugz.com/f/cases/13949 http://files.pharo.org/image/40/40238.zip

Sept. 20, 2014

[pharo-project/pharo-core]

by GitHub

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

Sept. 20, 2014

Re: [Pharo-dev] Parsing Pharo syntax to C/C++

by Alain Rastoul

Le 20/09/2014 02:33, phil(a)highoctane.be a Ã©crit : > We'll prevail! > > What we also need to do is to showcase the Smalltalk workflow and how > nice it is. > > We cannot gain mindshare by technical prowess only. > > Phil I totally agree with you, but I think that those technical advances are vital in current technology trends (saas, cloud, server side dev) and progress in this field is important. Despite the fact I think that Smalltalk still has an advance in object oriented systems/development, and offers a different perception it is hard to get the point about object system with people who are formatted by the hype or by their experience. Discussing with collegues about some smalltalk concepts is always interesting :)

Sept. 20, 2014

Re: [Pharo-dev] [Review: 11536] Add Stream >> printString:

by Esteban A. Maringolo

2014-09-19 20:59 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > > On Fri, Sep 19, 2014 at 1:19 AM, Max Leske <maxleske(a)gmail.com> wrote: >> >> This issue was more of a discussion between Camillo and Sven. They never >> reached a conclusion, so please take a look. Iâve compiled the transcript >> below. >> >> The issue isnât easy to solve and maybe we can just close it as ânot >> importantâ. > > > +1. But isn't the selector printString: broken? The selector sounds broken to me too. I always bring Dolphin to the discussion, but Dolphin streams had both #print:/#display: WriteStream>>#print: anObject anObject printOn: aStream. WriteStream>>#display: anObject anObject displayOn: aStream. But those are for printing/displaying the argument on the stream, which is not exactly the same as sending #asString and then then appending the result to receiver. So Eliot's #printAsString: seems to be the most intention revealing selector for such task. Regards!

Sept. 20, 2014

Re: [Pharo-dev] Parsing Pharo syntax to C/C++

by phil＠highoctane.be

Le 20 sept. 2014 02:11, "Alain Rastoul" <alf.mmm.cat(a)gmail.com> a Ã©crit : > > Le 15/09/2014 18:23, Eliot Miranda a Ã©crit : > >> I find this whole discussion depressing. It seems people would rather >> put their energy in chasing quick fixes or other technologies instead of >> contributing to the work that is being done in the existing VM. People >> discuss using LLVM as if the code generation capabilities inside Cog >> were somehow poor or have no chance of competing. Spur is around twice >> as fast as the current memory manager, has much better support for the >> FFI. ClÃ©ment and I, now with help from Ronie, are making excellent >> progress towards an adaptive optimizer/speculative inliner that will >> give us similar performance to V8 (the Google JavaScript VM, lead by >> Lars Bak, who implemented the HotSpot VM (Smalltalk and Java)) et al. >> We are trying to get person-power for a high-quality FFI and have a >> prototype for a non-blocking VM. When we succeed C won't be any better >> and so it won't be an interesting target. One will be able to program >> entirely in Smalltalk and get excellent performance. But we need >> effort. Collaboration. > > > Hi Eliot, > > Not everybody has the necessary skills to help and contribute to your work, my assembly skills are really faraway and outdated now (... little frustration here :( ... ) > but imho your work is unvaluable to pharo and smalltalk community > - just to mention it, I noticed a 30 to 50% gain in a small bench I wrote for fun recently (a very dumb chess pawn moves generator) with the last Spur vm > I was shocked :) > 64bits + x2 perfs + non blocking (or multi threaded?) vm are giant steps forward > that makes it possible for pharo smalltalk to compete with mainstream technologies We'll prevail! What we also need to do is to showcase the Smalltalk workflow and how nice it is. We cannot gain mindshare by technical prowess only. Phil > > Regards, > > Alain > >

Sept. 20, 2014

Re: [Pharo-dev] Parsing Pharo syntax to C/C++

by Alain Rastoul

Le 15/09/2014 18:23, Eliot Miranda a Ã©crit : > I find this whole discussion depressing. It seems people would rather > put their energy in chasing quick fixes or other technologies instead of > contributing to the work that is being done in the existing VM. People > discuss using LLVM as if the code generation capabilities inside Cog > were somehow poor or have no chance of competing. Spur is around twice > as fast as the current memory manager, has much better support for the > FFI. ClÃ©ment and I, now with help from Ronie, are making excellent > progress towards an adaptive optimizer/speculative inliner that will > give us similar performance to V8 (the Google JavaScript VM, lead by > Lars Bak, who implemented the HotSpot VM (Smalltalk and Java)) et al. > We are trying to get person-power for a high-quality FFI and have a > prototype for a non-blocking VM. When we succeed C won't be any better > and so it won't be an interesting target. One will be able to program > entirely in Smalltalk and get excellent performance. But we need > effort. Collaboration. Hi Eliot, Not everybody has the necessary skills to help and contribute to your work, my assembly skills are really faraway and outdated now (... little frustration here :( ... ) but imho your work is unvaluable to pharo and smalltalk community - just to mention it, I noticed a 30 to 50% gain in a small bench I wrote for fun recently (a very dumb chess pawn moves generator) with the last Spur vm I was shocked :) 64bits + x2 perfs + non blocking (or multi threaded?) vm are giant steps forward that makes it possible for pharo smalltalk to compete with mainstream technologies Regards, Alain

Sept. 20, 2014