- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

May 23, 2016

[pharo-project/pharo-core] 756471: 60029

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 7564717887459079fffd8bdf40f4ae6b69bd3a58 https://github.com/pharo-project/pharo-core/commit/7564717887459079fffd8bdf… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-23 (Mon, 23 May 2016) Changed paths: A Kernel.package/Boolean.class/instance/controlling/xor_.st M Manifest-Core.package/extension/TBehavior/instance/isManifest.st M Refactoring-Critics.package/RBDetectIfNoneRule.class/README.md M Refactoring-Critics.package/RBDetectIfNoneRule.class/instance/accessing/name.st M Refactoring-Critics.package/RBDetectIfNoneRule.class/instance/accessing/rationale.st M Refactoring-Critics.package/RBSmalltalkGlobalsRule.class/instance/accessing/name.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60028.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60029.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60028.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60029.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60029 18309 Typo in RBSmalltalkGlobalsRule https://pharo.fogbugz.com/f/cases/18309 18308 "Replaces detect:ifNone: by anySatisfy:" misleading rationale https://pharo.fogbugz.com/f/cases/18308 18247 deprecation warning on #isManifest for metaclasses https://pharo.fogbugz.com/f/cases/18247 18079 Boolean>>xor https://pharo.fogbugz.com/f/cases/18079 http://files.pharo.org/image/60/60029.zip

May 23, 2016

ConfigurationOfMerlin: to the guy who used a Halt as a cool way to let a message

by Esteban Lorenzano

donât! Iâm banning your configuration from MetaRepo because wellâ¦ it messes with the update process. yes, I could and will add more solid support, but seriously, this is very bad programming. Esteban

May 23, 2016

Re: [Pharo-dev] cleaning the Pharo Catalog

by Ben Coman

On Mon, May 23, 2016 at 4:04 PM, Cyril Ferlicot Delbecque <cyril.ferlicot(a)gmail.com> wrote: > > > On 23/05/2016 10:00, Stephan Eggermont wrote: >> Split into two categories? Those with full descriptions likely to load >> and those probably needing some updates? >> > > I like this option. Two tabs. A tab "PharoX" and a tab "Legacy" could be > an idea. But there are different levels of legacy. Once version back maybe not so bad. Several versions back likely worse. So maybe Pharo6, Pharo5, Legacy ? And it might be nice for Legacy to indicate which version Pharo they were associated with, but probably not enough value for such effort. cheers -ben > >> Stephan >> >> >> > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France >

May 23, 2016

Re: [Pharo-dev] Mocketry names again

by Tudor Girba

Yuppee! Thanks :) Doru > On May 23, 2016, at 12:18 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > And done. Version 3.4 deprecates "should got" and introduces "should receive". > All docs are updated. > > Prebuilt PDF can found here https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… > > 2016-05-18 11:59 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > So at the end of week I will rename "should got" into "should receive" > > 2016-04-27 23:39 GMT+02:00 Carlos Lombardi <carlombardi(a)gmail.com>: > Hi again, > > ok, just to have coherence between the names for the two possible outcomes of a method, you could use #beReturnedBy instead of #beReturnedFrom: . You would have #beReturnedBy: and #beRaisedBy: > > On Wed, Apr 27, 2016 at 10:00 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2016-04-27 0:33 GMT+02:00 Carlos Lombardi <carlombardi(a)gmail.com>: > ... maybe > > #result should beTheResultOf: [mock someMessage]. > #result should not beTheResultOf: [mock anotherMessage]. > > It's nice.I think "The" can be omitted: > > #result should beResultOf: [mock someMessage]. > > But anyway I use word #return because there are different types of result: value return and error signal. There is no expression for last case but it would be like: > > anError should beRaisedBy: [mock someMessage] > > > -- www.tudorgirba.com www.feenk.com "Speaking louder won't make the point worthier."

May 23, 2016

Re: [Pharo-dev] Mocketry names again

by Denis Kudriashov

And done. Version 3.4 deprecates "should got" and introduces "should receive". All docs are updated. Prebuilt PDF can found here https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… 2016-05-18 11:59 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > So at the end of week I will rename "should got" into "should receive" > > 2016-04-27 23:39 GMT+02:00 Carlos Lombardi <carlombardi(a)gmail.com>: > >> Hi again, >> >> ok, just to have coherence between the names for the two possible >> outcomes of a method, you could use #beReturnedBy instead of >> #beReturnedFrom: . You would have #beReturnedBy: and #beRaisedBy: >> >> On Wed, Apr 27, 2016 at 10:00 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> >>> >>> 2016-04-27 0:33 GMT+02:00 Carlos Lombardi <carlombardi(a)gmail.com>: >>> >>>> ... maybe >>>> >>>> #result should beTheResultOf: [mock someMessage]. >>>> #result should not beTheResultOf: [mock anotherMessage]. >>>> >>> >>> It's nice.I think "The" can be omitted: >>> >>> #result should beResultOf: [mock someMessage]. >>> >>> >>> But anyway I use word #return because there are different types of >>> result: value return and error signal. There is no expression for last case >>> but it would be like: >>> >>> anError should beRaisedBy: [mock someMessage] >>> >>> >> >

May 23, 2016

Re: [Pharo-dev] cleaning the Pharo Catalog

by Cyril Ferlicot Delbecque

On 23/05/2016 10:00, Stephan Eggermont wrote: > Split into two categories? Those with full descriptions likely to load > and those probably needing some updates? > I like this option. Two tabs. A tab "PharoX" and a tab "Legacy" could be an idea. > Stephan > > > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

May 23, 2016

[pharo-project/pharo-core]

by GitHub

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

May 23, 2016

[pharo-project/pharo-core] e22bb5: 60028

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: e22bb56e311438134062dea8f1c80822f144c27c https://github.com/pharo-project/pharo-core/commit/e22bb56e311438134062dea8… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-23 (Mon, 23 May 2016) Changed paths: M Collections-Abstract.package/Collection.class/instance/math functions/stdev.st R Kernel.package/Object.class/instance/updating/noteSelectionIndex_for_.st M Morphic-Widgets-Pluggable.package/PluggableListMorph.class/instance/updating/verifyContents.st M Refactoring-Core.package/RBAbstractClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBAbstractInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBAbstractVariablesRefactoring.class/README.md M Refactoring-Core.package/RBAccessorClassRefactoring.class/README.md M Refactoring-Core.package/RBAddClassRefactoring.class/README.md M Refactoring-Core.package/RBAddClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBAddInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBAddMethodRefactoring.class/README.md M Refactoring-Core.package/RBAddParameterRefactoring.class/README.md M Refactoring-Core.package/RBCategoryRegexRefactoring.class/README.md M Refactoring-Core.package/RBChangeMethodNameRefactoring.class/README.md M Refactoring-Core.package/RBChildrenToSiblingsRefactoring.class/README.md M Refactoring-Core.package/RBClassRefactoring.class/README.md M Refactoring-Core.package/RBClassRegexRefactoring.class/README.md M Refactoring-Core.package/RBCreateAccessorsForVariableRefactoring.class/README.md M Refactoring-Core.package/RBExpandReferencedPoolsRefactoring.class/README.md M Refactoring-Core.package/RBExtractMethodRefactoring.class/README.md M Refactoring-Core.package/RBExtractMethodToComponentRefactoring.class/README.md M Refactoring-Core.package/RBExtractToTemporaryRefactoring.class/README.md M Refactoring-Core.package/RBGenerateEqualHashRefactoring.class/README.md M Refactoring-Core.package/RBGeneratePrintStringRefactoring.class/README.md M Refactoring-Core.package/RBInlineAllSendersRefactoring.class/README.md M Refactoring-Core.package/RBInlineMethodFromComponentRefactoring.class/README.md M Refactoring-Core.package/RBInlineMethodRefactoring.class/README.md M Refactoring-Core.package/RBInlineParameterRefactoring.class/README.md M Refactoring-Core.package/RBInlineTemporaryRefactoring.class/README.md M Refactoring-Core.package/RBMethodName.class/README.md M Refactoring-Core.package/RBMethodRefactoring.class/README.md M Refactoring-Core.package/RBMoveMethodRefactoring.class/README.md M Refactoring-Core.package/RBMoveVariableDefinitionRefactoring.class/README.md M Refactoring-Core.package/RBPrettyPrintCodeRefactoring.class/README.md M Refactoring-Core.package/RBProtectInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBProtocolRegexRefactoring.class/README.md M Refactoring-Core.package/RBPullUpClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBPullUpInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBPullUpMethodRefactoring.class/README.md M Refactoring-Core.package/RBPushDownClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBPushDownInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBPushDownMethodRefactoring.class/README.md M Refactoring-Core.package/RBRefactoring.class/README.md M Refactoring-Core.package/RBRefactoringManager.class/README.md M Refactoring-Core.package/RBRefactoryTyper.class/README.md M Refactoring-Core.package/RBRegexRefactoring.class/README.md M Refactoring-Core.package/RBRemoveClassRefactoring.class/README.md M Refactoring-Core.package/RBRemoveClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBRemoveInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBRemoveMethodRefactoring.class/README.md M Refactoring-Core.package/RBRemoveParameterRefactoring.class/README.md M Refactoring-Core.package/RBRenameClassRefactoring.class/README.md M Refactoring-Core.package/RBRenameClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBRenameInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBRenameMethodRefactoring.class/README.md M Refactoring-Core.package/RBRenameTemporaryRefactoring.class/README.md M Refactoring-Core.package/RBSourceRegexRefactoring.class/README.md M Refactoring-Core.package/RBSplitCascadeRefactoring.class/README.md M Refactoring-Core.package/RBSplitCascadeRefactoring.class/instance/preconditions/findMessageNodes.st A Refactoring-Core.package/RBSplitCascadeRefactoring.class/instance/printing/storeOn_.st M Refactoring-Core.package/RBSplitClassRefactoring.class/README.md M Refactoring-Core.package/RBTemporaryToInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBVariableRefactoring.class/README.md A Refactoring-Tests-Core.package/RBSplitCascadeRefactoringTest.class/README.md A Refactoring-Tests-Core.package/RBSplitCascadeRefactoringTest.class/definition.st A Refactoring-Tests-Core.package/RBSplitCascadeRefactoringTest.class/instance/data/methodWithCascades.st A Refactoring-Tests-Core.package/RBSplitCascadeRefactoringTest.class/instance/tests/testSplitCascadeRefactoring.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60027.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60028.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60027.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60028.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60028 18297 RBSplitCascadeRefactoring broken https://pharo.fogbugz.com/f/cases/18297 18277 Add Class comments to Refactoring-Core-Refactorings classes https://pharo.fogbugz.com/f/cases/18277 18299 Add Class comments to Refactoring-Core-Supportclasses https://pharo.fogbugz.com/f/cases/18299 18293 Add a comment to Collection>>#stdev https://pharo.fogbugz.com/f/cases/18293 18294 Remove Object >> #noteSelectionIndex:for: https://pharo.fogbugz.com/f/cases/18294 http://files.pharo.org/image/60/60028.zip

May 23, 2016

Re: [Pharo-dev] cleaning the Pharo Catalog

by Stephan Eggermont

On 23/05/16 09:53, Esteban Lorenzano wrote: > Hi guys, > > I will update the Catalog for Pharo 6 and I was wondering if we should keep the âUnsortedâ categoryâ¦ this corresponds with projects present in old MetacelloRepository repo, I added it at the beginning because I did not want those project to be lost, but in fact they are more or less abandonware and definitively, they were not very well kept (no descriptions, no tags and even worst, many of them will not load fine). > So what do you think? should I keep them? Split into two categories? Those with full descriptions likely to load and those probably needing some updates? Stephan

May 23, 2016