- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] OCCompilerASTPlugin

by Marcus Denker

> On 04 Sep 2016, at 20:48, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > I have one question about Opal Compiler. > > I would like do an AST transformation before using the compiler. If I > understand correctly, I have to built a subclass of > OCCompilerASTPlugin ? Is it correct ? Yes. See the example ASTPluginMeaningOfLife Plugins are not active by default, you need to compile with a compiler that includes your plugin. e.g. add on the class side compiler "the example plugin is active for this class" ^super compiler addPlugin: ASTPluginMeaningOfLife. to enable it for this hierarchy. ( see ASTTransformExamplePluginActive ) > Any documentation more update about Opal than this : > https://github.com/SquareBracketAssociates/PharoLimbo/tree/master/Opal There is the paper: https://marcusdenker.de/publications/Bera13a-OpalIWST.pdf But it is not a tutorial. Marcus

Sept. 7, 2016

Re: [Pharo-dev] SmallLintRule RBGuardingClauseRule and RBGuardClauseRule

by Marcus Denker

> On 05 Sep 2016, at 09:15, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > We have to similar rules > RBGuardClauseRule and RBGuardingClauseRule > One is a ParseTreeLintRule, the other one is a TransformationRule. > > I don't know why we have to at all. > One rule was "disabled" (or not chown) in the CriticsBrowser because it > was removed from the set of all rules before opening CriticsBrowser > (see method #allGoodRules). > > In the past, monty fixed the class comment and #rational for class > RBGuardClauseRule to correctly explain what this rule is about. > This of course now differes from the similar rule RBGuardingClauseRule. > > 1. Why do we have both (ok, on can only select the rule violation, whereas the other on > does not select it but shows the possible transformation > 2. why is the second one now in the set of all rules used by CriticsBrowser > 3. what to do ? Remove one, fix the comment and #rational for the second one? > Yes, we should clean upâ¦ I would remove one. Marcus

Sept. 7, 2016

[pharo-project/pharo-core]

by GitHub

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

Sept. 7, 2016

[pharo-project/pharo-core] 5917ae: 60207

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 5917aebcf7d2b406f2ed921c967f85c613748ad9 https://github.com/pharo-project/pharo-core/commit/5917aebcf7d2b406f2ed921c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-07 (Wed, 07 Sep 2016) Changed paths: M ConfigurationOfFlatQA.package/ConfigurationOfFlatQA.class/instance/symbolic versions/stable_.st A ConfigurationOfFlatQA.package/ConfigurationOfFlatQA.class/instance/versions/versionv3%5F2%5F7_.st M DebuggerActions.package/BrowseDebugAction.class/class/actions creation/debugActionsFor_.st M DebuggerActions.package/DebugAction.class/definition.st M DebuggerActions.package/DebugAction.class/instance/accessing/defaultKeyText.st A DebuggerActions.package/DebugAction.class/instance/accessing/defaultKeymap.st M DebuggerActions.package/DebugAction.class/instance/accessing/keyText.st M DebuggerActions.package/DebugAction.class/instance/accessing/keyText_.st A DebuggerActions.package/DebugAction.class/instance/accessing/keymap.st A DebuggerActions.package/DebugAction.class/instance/accessing/keymap_.st R DebuggerActions.package/RestartDebugAction.class/instance/accessing/defaultKeyText.st A DebuggerActions.package/RestartDebugAction.class/instance/accessing/defaultKeymap.st R DebuggerActions.package/ResumeDebugAction.class/instance/accessing/defaultKeyText.st A DebuggerActions.package/ResumeDebugAction.class/instance/accessing/defaultKeymap.st R DebuggerActions.package/StepIntoDebugAction.class/instance/accessing/defaultKeyText.st A DebuggerActions.package/StepIntoDebugAction.class/instance/accessing/defaultKeymap.st R DebuggerActions.package/StepOverDebugAction.class/instance/accessing/defaultKeyText.st A DebuggerActions.package/StepOverDebugAction.class/instance/accessing/defaultKeymap.st R DebuggerActions.package/StepThroughDebugAction.class/instance/accessing/defaultKeyText.st A DebuggerActions.package/StepThroughDebugAction.class/instance/accessing/defaultKeymap.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60206.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60207.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60206.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60207.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Debugger.package/SpecDebuggerStack.class/instance/updating/updateDebuggingActions.st R Spec-Debugger.package/extension/DebugAction/instance/shortcutCommand.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code search/browseClassReferencesShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code search/browseMethodHierarchyShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - debugger/restartExecutionShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - debugger/resumeExecutionShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - debugger/stepIntoShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - debugger/stepOverShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - debugger/stepThroughShortcut.st M Traits.package/TClass.class/instance/copying/duplicateClassWithNewName_.st Log Message: ----------- 60207 19054 QA 3.2.7 https://pharo.fogbugz.com/f/cases/19054 19050 Copying a class doesnt replicate the pool dictionary definitions https://pharo.fogbugz.com/f/cases/19050 19044 DebugAction should use key-mappings and not characters to indicate shortcuts https://pharo.fogbugz.com/f/cases/19044 http://files.pharo.org/image/60/60207.zip

Sept. 7, 2016

Re: [Pharo-dev] current athens configuration

by Marcus Denker

> On 07 Sep 2016, at 09:28, stepharo <stepharo(a)free.fr> wrote: > > >> I would like to add a fix for >> issue >> 18657 <https://pharo.fogbugz.com/f/cases/18657/Rendering-text-in-athens-is-broken> Rendering text in athens is broken >> >> But there are many changes and even new configurations of athens >> in its repository. Those changes aren't yet in Pharo 6. >> And I don't know which one to take or where to add this fix. > Oops me neither. > If people do not push changes to Pharo they slip under our radar. This idea of âexternalâ repositories completely breaks down as soon as there is no maintainer. Marcus

Sept. 7, 2016

Re: [Pharo-dev] current athens configuration

by stepharo

> I would like to add a fix for > issue > 18657 > <https://pharo.fogbugz.com/f/cases/18657/Rendering-text-in-athens-is-broken> > Rendering text in athens is broken > > But there are many changes and even new configurations of athens > in its repository. Those changes aren't yet in Pharo 6. > And I don't know which one to take or where to add this fix. Oops me neither. If people do not push changes to Pharo they slip under our radar. > Can people who added the latest athens changes (and configuration) > please comment on what changes should go into pharo 6 > > thanks > nicolai

Sept. 7, 2016

Re: [Pharo-dev] finalization

by Ben Coman

I'm documenting what I'm learning in a format for a blog post that might be the basis for something. cheers -ben On Wed, Sep 7, 2016 at 3:40 AM, stepharo <stepharo(a)free.fr> wrote: > Ben > > no stress. Now what I would love is an example that we can put in the uFFI > chapter :) > > Stef > > > Le 6/9/16 Ã 17:32, Ben Coman a Ã©crit : > >> 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

current athens configuration

by Nicolai Hess

I would like to add a fix for issue 18657 <https://pharo.fogbugz.com/f/cases/18657/Rendering-text-in-athens-is-broken> Rendering text in athens is broken But there are many changes and even new configurations of athens in its repository. Those changes aren't yet in Pharo 6. And I don't know which one to take or where to add this fix. Can people who added the latest athens changes (and configuration) please comment on what changes should go into pharo 6 thanks nicolai

Sept. 6, 2016

Re: [Pharo-dev] Can Sound depend on Jobs?

by stepharo

close to the sound package. Le 5/9/16 Ã 19:18, Sean P. DeNigris a Ã©crit : > Sean P. DeNigris wrote >> it seems a third package (with only one method in it!) is in order. > Any ideas on where to commit the JobsSound package? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Can-Sound-depend-on-Jobs-tp4914083p4914210.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Sept. 6, 2016

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

by stepharo

> > > What image version ? > > We had an issue for a similar case (the class /instance variable names > were copied *and* renamed too) yes I faced this problem it was really strange :) > > 18957 > <https://pharo.fogbugz.com/f/cases/18957/Class-copy-should-not-change-the-na…> > 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). > >

Sept. 6, 2016