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

Context representation in current VM

by Martin McClure

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. Thanks, -Martin

Sept. 28, 2014

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

by Max Leske

On 26.09.2014, at 20:27, Max Leske <maxleske(a)gmail.com> wrote: > > On 26.09.2014, at 18:44, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 26 Sep 2014, at 18:21, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >>> >>> >>> On Fri, Sep 26, 2014 at 6:20 AM, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> On 20.09.2014, at 03:02, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> >>>> 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. >>> >>> Ok, so how about adding WriteStream>>printAsString:? Implementation: >>> >>> printAsString: anObject >>> self nextPutAll: anObject asString >>> >>> If you add this it also needs to be added to whatever the transcript streams are. The two should have the same protocol for writing. Right now there are a number of missing methods on the transcript side. >> >> I still don't like it, we're just adding methods, making the API fatter, for what exactly ? >> >> What is the difference between >> >> stream printAsString: foo >> >> and >> >> stream << foo asString > > None really. Actually I donât quite see why #asString should ever be sent (except for during error handling maybe). I usually override #printOn: for displaying information about an object during development and use a specific implementation when I want to store an object on a stream. So I rarely need #asString in combination with streams. > > >> >> ? >> >> Do we really need this ? > > No, I guess not. It has worked fine so far. But since the discussion was opened I thought Iâd push a little :) > > So: anybody opposed to closing this issue? > Closed as âwonât fix". > Cheers, > Max > >> >> Sven

Sept. 28, 2014

Re: [Pharo-dev] csv2html the Pharo version

by Andreas Wacknitz

Am 27.09.2014 um 00:53 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > Hi Andreas, > > On 26 Sep 2014, at 22:25, Andreas Wacknitz <a.wacknitz(a)gmx.de> wrote: > >> Am 18.09.2014 um 10:28 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >>> Hi, >>> >>> Today I came across some bash code on a web page that loves Smalltalk, ah the horror ;-) >>> >>> http://car.mines-douai.fr/2014/09/csv2html/ >>> >>> The goal is to make it easier to look at CSV data, for which a conversion to HTML was done. To just look at CSV data in a nice tabular form, we do not have to leave Pharo at all. >>> >>> MultiColumnListModel new >>> items: (FileLocator desktop / 'test.csv' readStreamDo: [ :in | >>> (NeoCSVReader on: in) emptyFieldValue: ''; upToEnd ]); >> What version of NeoCSV has >>emptyFieldValue:? >> (And where can I get it?) >> I havenât seen this method yetâ¦ > > It was in #bleedingEdge, I made a new #stable version of ConfigurationOfNeoCSV (v11). You can use the Configuration Browser in Pharo 3.0 or load via Gofer (the project is on StHub as well). > > HTH, > > Sven > > > I got it via the newest Moose. Thanks a lot! Andreas

Sept. 27, 2014

[pharo-project/pharo-core]

by GitHub

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

Sept. 27, 2014

[pharo-project/pharo-core] 237530: 40264

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 237530b9fdc83af0bdfad5ec13928f3ce46c945f https://github.com/pharo-project/pharo-core/commit/237530b9fdc83af0bdfad5ec… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-27 (Sat, 27 Sep 2014) Changed paths: M Collections-Abstract.package/SequenceableCollection.class/class/stream creation/new_streamContents_.st A CollectionsTests.package/TSequencedConcatenationTest.class/instance/tests - streaming/testNewStreamContentsReturnsCollectionOfCorrectSize.st A CollectionsTests.package/WriteStreamTest.class/instance/testing/testContentsReturnCollectionOfCorrectSize.st A CollectionsTests.package/WriteStreamTest.class/instance/testing/testContentsReturnCollectionOfCorrectSizeAfterSettingPosition.st A RPackage-Core.package/extension/TClassDescription/instance/definedSelectors.st A RPackage-Core.package/extension/TClassDescription/instance/extensionSelectors.st M RPackage-Tests.package/RPackageReadOnlyCompleteSetupTest.class/instance/setup/setUp.st A RPackage-Tests.package/RPackageReadOnlyCompleteSetupTest.class/instance/test situation/testDefinedSelectors.st A RPackage-Tests.package/RPackageReadOnlyCompleteSetupTest.class/instance/test situation/testExtensionSelectors.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script264.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40264.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/MessageBrowser.class/instance/initialization/initializePresenter.st M Spec-Tools.package/MessageBrowser.class/instance/private/accept_notifying_.st Log Message: ----------- 40264 13867 MessageBrowser does not inform about certain syntax error https://pharo.fogbugz.com/f/cases/13867 13293 We should add definedSelectors and extensionSelectors to ClassDescription https://pharo.fogbugz.com/f/cases/13293 13934 Extra characters in string returned by String class>>new:streamContents: https://pharo.fogbugz.com/f/cases/13934 http://files.pharo.org/image/40/40264.zip

Sept. 27, 2014

Re: [Pharo-dev] Copy class needs more information to do a good job

by Marcus Denker

On 26 Sep 2014, at 16:10, Camille Teruel <camille.teruel(a)gmail.com> wrote: > Another annoying thing is that when you copy a hierarchy you have to change the subclass relationships manually. > For example, if you select two classes -- Superclass Subclass -- and copy them you end up with NewSubclass as a subclass of Superclass instead of NewSuperclass. > When copying a big hierarchy it's tiresome. > We need to distinguish between #copy: low level copy of classes, as opposed to the tool, which should provide a nice dialog (copy comment yes, no, copy superclass hierarchy, where to put the copyâ¦) Marcus > On 26 sept. 2014, at 14:08, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> Copy class needs more information to do a good job >> >> At the moment, the copy class command only asks for the name of the new class. That is not enough information. There have been a number of issues posted about copying (or not) of the class comment, Issue 13247, 10039, 12294 and 12265. >> >> Other information that can be helpful is the package where the new class should be. I nearly never need a copy in the package where the original was. >> >> Cheers, >> Stephan >> >> https://pharo.fogbugz.com/default.asp?14084 > >

Sept. 27, 2014

Re: [Pharo-dev] Nautilus roadmap / icons

by Marcus Denker

On 26 Sep 2014, at 20:44, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Marcus, > > On Thu, Sep 25, 2014 at 11:29 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 25 Sep 2014, at 23:02, phil(a)highoctane.be wrote: > > > Well, the full story is that the decompiler is now gone with Opal. > > > There is a decompiler again in Pharo4 > > > So, there were 3 in the beginning. So, of course with 2, this becomes a switch. > > > > Why no decompiler anymore, for the layman I am? > > > The *option* of showing decompiled code in the browser: Honestly, I do not get > why this was useful, ever. > > I can think of three reasons. > > 1. mutable literals. using the decompiler is a quick way to check if a literal has been corrupted/modified > > 2. if you're working on the decompiler this is convenient > Yes, but all this does not mean that there need to be a button always visible for itâ¦ (and maybe GTInspector already provides the perfect tool for it? I guess it does: Decompiler can define a view for CompiledMethod, it is added as a tab, the tabs let you switch easily between code, AST, IR, CM Header and everyone else who defines an inspector view for the method) > 3. when Dan's encode temp names in trailer and decompile scheme was being developed/used there would be no need to display sources We removed thatâ¦ Marcus

Sept. 27, 2014

[pharo-project/pharo-core]

by GitHub

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

Sept. 27, 2014

[pharo-project/pharo-core] 4bc2e0: 40263

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 4bc2e0b91ee3a0c12c74fde761c55d27d46a962a https://github.com/pharo-project/pharo-core/commit/4bc2e0b91ee3a0c12c74fde7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-27 (Sat, 27 Sep 2014) Changed paths: M Collections-Strings.package/String.class/instance/accessing/do_toFieldNumber_.st M Collections-Strings.package/String.class/instance/accessing/tabDelimitedFieldsDo_.st M Collections-Strings.package/String.class/instance/converting/splitInteger.st M Collections-Strings.package/String.class/instance/copying/padded_to_with_.st M FuelTests.package/FLSerializationTest.class/definition.st A FuelTests.package/FLSerializationTest.class/instance/accessing/traits.st M FuelTests.package/FLSerializationTest.class/instance/traits-factory/cleanUpTraits.st M FuelTests.package/FLSerializationTest.class/instance/traits-factory/newTraitSuffixed_.st R Morphic-Widgets-Pluggable.package/PluggablePanelMorph.class/README.md R Morphic-Widgets-Pluggable.package/PluggablePanelMorph.class/definition.st R Morphic-Widgets-Pluggable.package/PluggablePanelMorph.class/instance/accessing/getChildrenSelector.st R Morphic-Widgets-Pluggable.package/PluggablePanelMorph.class/instance/accessing/getChildrenSelector_.st R Morphic-Widgets-Pluggable.package/PluggablePanelMorph.class/instance/accessing/model.st R Morphic-Widgets-Pluggable.package/PluggablePanelMorph.class/instance/accessing/model_.st R Morphic-Widgets-Pluggable.package/PluggablePanelMorph.class/instance/update/update_.st M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/moveInPackage.st A NautilusRefactoring.package/extension/RBSwapMethodRefactoring/instance/whatToDisplayIn_.st M SUnit-UI.package/TestRunner.class/instance/building/buildButtons.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script263.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/scriptnil.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40263.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40263 13742 PluggablePanelMorph looks empty and is only used once in the system https://pharo.fogbugz.com/f/cases/13742 14094 Deprecate a few unused String methods https://pharo.fogbugz.com/f/cases/14094 13337 Moving a class to a package does not work anymore https://pharo.fogbugz.com/f/cases/13337 13331 moving a group of methods class side raises an error https://pharo.fogbugz.com/f/cases/13331 11475 Optimize FuelTests >> #tearDownTraits https://pharo.fogbugz.com/f/cases/11475 http://files.pharo.org/image/40/40263.zip

Sept. 27, 2014

New Cog VMs available

by Eliot Miranda

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3083 CogVM source as per VMMaker.oscog-eem.886/r3083 Fix regression in V3 become youngReferrers management in VMMaker.oscog-eem.882. We /must/ prune young referrers if mapObjectReferencesInMachineCodeForBecome removes a cog method from youngReferrers because it may get added back and youngReferrers cannot contain duplicates. Spur: Fix bug in sweepToFollowForwardersForPigCompact which failed to update and answer lowest forwarder. Fixes numForwarders == 0 assert failures. Fix bug with become and class table not removing classes which become causes them to be unhashed. Fix bogus assert fail in synchronousSignal:. Refactor following code into ensureSemaphoreForwardedThroughContext: and fix the assert there-in. Use rawOverflowSlotsOf: in bytesInObject:. Make a little more progress on Spur image segment support. Provide a classTableEntriesDo: and use it to compute an arrayOfUnmarkedClasses. Cogit: Make sure voidImplicitReceiverCacheAt: sets codeModified if IRCs are inline. Make sure freeMethod: clears cmRefersToYoung Fix assert in cogitPostGCAction: that would fire erroneously in Spur become. Move evaluation of Cogit primitive desacriptor enabled function from initialization to just-in-time, and add enablers on SmallInteger primitives to ensure they are applied only to SmallInteger receivers (falling back to interpreter prims if not). Hence fix Cog for 4.1 (e.g. MuO) images. Back out of saneMethodClassAssociation assert in initialPCForHeader:method:. Newspeak falls foul of this. Make sure that the method is set on returning from a callback. Fixes MNUs of atAddress: in exampleCqsort in the stack VMs. Fix bugs in scripts and Windows manifests. -- best, Eliot

Sept. 26, 2014