- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ensureCreateDirectory?

by Norbert Hartl

Stef, I really donât want to stretch this into an argue â¦. but I have problems understanding that. There are refactorings of method selectors because it is said it is important that includesSubString: is written as includesSubstring: and there are other examples. Now we have a selector that people find confusing and that is not important? I donât understand it and the only difference I can see by now is the way you or your team is involved in the action. So the only thing I would understand is sensitivities meaning you are sick of complaints regarding your work. Otherwise I donât understand that. Norbert Am 25.10.2013 um 15:04 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > can we focus on real problems? > The method has a comment. > > Stef > > On Oct 25, 2013, at 10:39 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 25.10.2013 um 10:11 schrieb Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> >>> So action=create object=directory >>> you want to be sure that you create a directory? >>> What if it already exists? >>> Since you want to be sure to create, will you erase and re-create? >>> You see the kind of misunderstanding this could create... >>> IOW, self ensureCreateMisunderstanding >>> >> +1 I didnât like it in the first place. It is just confusing. And probably an example how hard it can be if two or more non-native speaker try to find something that makes sense. >> >> Norbert >>> >>> 2013/10/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> Consistency >>> ensureActionObject >>> >>> ensureCreateDirectory >>> ensureCreateFile >>> >>> We discuss a lot with camillo when we did it and I think that this is good right now. >>> >>> > Out of curiosity, what was the motivation behind Issue 10924: Simplifying >>> > ensure* and create protocol? >>> > >>> > For me #ensureCreateDirectory is less intention revealing than >>> > #ensureDirectory because the "ensure" means "create only if necessary", not >>> > "definitely create" a directory. What am I missing? Thanks. >>> > >>> > >>> > >>> > ----- >>> > Cheers, >>> > Sean >>> > -- >>> > View this message in context: http://forum.world.st/ensureCreateDirectory-tp4716925.html >>> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> > >>> >>> >>> >> >

Oct. 25, 2013

Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523

by Marcus Denker

I did it because they are the only ones. Yes, we need to have them at some point. But having two baselines but nothing else makes no sense. And we need to be able to organise package better, even with the package tags there is too much in the left pane. On 25 Oct 2013 at 15:19:02, Christophe Demarey (christophe.demarey(a)inria.fr) wrote: > >Why do we need to remove configurations of projects loaded into the image? >I would say the opposite: all projects in the image should have their configuration loaded. It is part of the project. > >Le 25 oct. 2013 Ã 14:00, GitHub a Ã©crit : >> 12005 unload BaselineOfFileTree, BaselineOfMetacello >> https://pharo.fogbugz.com/f/cases/12005 > > >- smime.p7s, 6 KB

Oct. 25, 2013

Re: [Pharo-dev] ensureCreateDirectory?

by Nicolas Cellier

What are real problems exactly? If you are going to open each and every method to read the comment or the code instead of trusting the name, IMHO that is going to be a real problem. If the focus shall be on real problems, then why change APIs which are not a real problem? 2013/10/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > can we focus on real problems? > The method has a comment. > > Stef > > On Oct 25, 2013, at 10:39 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 25.10.2013 um 10:11 schrieb Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com>: > > So action=create object=directory > you want to be sure that you create a directory? > What if it already exists? > Since you want to be sure to create, will you erase and re-create? > You see the kind of misunderstanding this could create... > IOW, self ensureCreateMisunderstanding > > +1 I didnât like it in the first place. It is just confusing. And probably > an example how hard it can be if two or more non-native speaker try to find > something that makes sense. > > Norbert > > > 2013/10/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> Consistency >> ensureActionObject >> >> ensureCreateDirectory >> ensureCreateFile >> >> We discuss a lot with camillo when we did it and I think that this is >> good right now. >> >> > Out of curiosity, what was the motivation behind Issue 10924: >> Simplifying >> > ensure* and create protocol? >> > >> > For me #ensureCreateDirectory is less intention revealing than >> > #ensureDirectory because the "ensure" means "create only if necessary", >> not >> > "definitely create" a directory. What am I missing? Thanks. >> > >> > >> > >> > ----- >> > Cheers, >> > Sean >> > -- >> > View this message in context: >> http://forum.world.st/ensureCreateDirectory-tp4716925.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com <http://nabble.com/>. >> > >> >> >> > > >

Oct. 25, 2013

[pharo-project/pharo-core] fdec0d: 30524

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: fdec0d85c64952aa500fd73ab1818bbcec3c8ae8 https://github.com/pharo-project/pharo-core/commit/fdec0d85c64952aa500fd73a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-25 (Fri, 25 Oct 2013) Changed paths: M RPackage-Core.package/RPackage.class/instance/updating/updateDefinedClassNamed_withNewName_.st A RPackage-Core.package/RPackageTag.class/instance/updating/updateDefinedClassNamed_withNewName_.st M RPackage-SystemIntegration.package/extension/RPackageOrganizer/instance/systemClassRenamedActionFrom_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script179.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30524.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R UIManager.package/CommandLineUIManager.class/class/as yet unclassified/uiSettingsOn_.st A UIManager.package/CommandLineUIManager.class/class/settings/uiSettingsOn_.st R UIManager.package/CommandLineUIManager.class/instance/ui requests/progressInitiationExceptionDefaultAction_.st R UIManager.package/DummySystemProgressItem.class/instance/as yet unclassified/doesNotUnderstand_.st A UIManager.package/DummySystemProgressItem.class/instance/reflective operations/doesNotUnderstand_.st R UIManager.package/DummyUIManager.class/instance/as yet unclassified/multiLineRequest_initialAnswer_answerHeight_.st A UIManager.package/DummyUIManager.class/instance/ui requests/multiLineRequest_initialAnswer_answerHeight_.st R UIManager.package/DummyUIManager.class/instance/ui requests/progressInitiationExceptionDefaultAction_.st R UIManager.package/ErrorNonInteractive.class/class/as yet unclassified/signalForException_.st A UIManager.package/ErrorNonInteractive.class/class/signalling/signalForException_.st Log Message: ----------- 30524 11938 A lot of empty Spec packages which should be deleted https://pharo.fogbugz.com/f/cases/11938 12003 UIManager small cleanup https://pharo.fogbugz.com/f/cases/12003 12006 RPackage/RPackageTag get out of sync on class rename https://pharo.fogbugz.com/f/cases/12006/ http://files.pharo.org/image/30/30524.zip

Oct. 25, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 25, 2013

Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523

by Christophe Demarey

Why do we need to remove configurations of projects loaded into the image? I would say the opposite: all projects in the image should have their configuration loaded. It is part of the project. Le 25 oct. 2013 Ã 14:00, GitHub a Ã©crit : > 12005 unload BaselineOfFileTree, BaselineOfMetacello > https://pharo.fogbugz.com/f/cases/12005

Oct. 25, 2013

Re: [Pharo-dev] ensureCreateDirectory?

by StÃ©phane Ducasse

can we focus on real problems? The method has a comment. Stef On Oct 25, 2013, at 10:39 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 25.10.2013 um 10:11 schrieb Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > >> So action=create object=directory >> you want to be sure that you create a directory? >> What if it already exists? >> Since you want to be sure to create, will you erase and re-create? >> You see the kind of misunderstanding this could create... >> IOW, self ensureCreateMisunderstanding >> > +1 I didnât like it in the first place. It is just confusing. And probably an example how hard it can be if two or more non-native speaker try to find something that makes sense. > > Norbert >> >> 2013/10/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> Consistency >> ensureActionObject >> >> ensureCreateDirectory >> ensureCreateFile >> >> We discuss a lot with camillo when we did it and I think that this is good right now. >> >> > Out of curiosity, what was the motivation behind Issue 10924: Simplifying >> > ensure* and create protocol? >> > >> > For me #ensureCreateDirectory is less intention revealing than >> > #ensureDirectory because the "ensure" means "create only if necessary", not >> > "definitely create" a directory. What am I missing? Thanks. >> > >> > >> > >> > ----- >> > Cheers, >> > Sean >> > -- >> > View this message in context: http://forum.world.st/ensureCreateDirectory-tp4716925.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >> >> >> >

Oct. 25, 2013

Re: [Pharo-dev] RB AST node positions off by one or more characters with Opal ?

by Marcus Denker

On 25 Oct 2013 at 11:16:35, Goubier Thierry (thierry.goubier(a)cea.fr) wrote: > >Hi all, > >has anybody noticed that, when getting node positions from a RB parse of >the AST, they seem to be off by one character or more? It happens in >smart suggestions type of commands for me, but it seems to also happens >when the compiler tries to remove unused temporaries and garbles up the >temp declaration line? > That one i have seen, yes.Â I will put it on the list of things to look at soon(ish) >(In the latest 3.0, of course :))

Oct. 25, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 25, 2013

[pharo-project/pharo-core] 4021f3: 30523

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 4021f31ef110a3f16862ef02329c66f4e04ffa40 https://github.com/pharo-project/pharo-core/commit/4021f31ef110a3f16862ef02… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-25 (Fri, 25 Oct 2013) Changed paths: R BaselineOfFileTree.package/BaselineOfFileTree.class/README.md R BaselineOfFileTree.package/BaselineOfFileTree.class/definition.st R BaselineOfFileTree.package/BaselineOfFileTree.class/instance/baseline/baseline_.st R BaselineOfMetacello.package/BaselineOfMetacello.class/README.md R BaselineOfMetacello.package/BaselineOfMetacello.class/definition.st R BaselineOfMetacello.package/BaselineOfMetacello.class/instance/baseline/baseline_.st R BaselineOfMetacello.package/BaselineOfMetacello.class/instance/doits/gemstone10beta311PostLoadDoIt.st R BaselineOfMetacello.package/BaselineOfMetacello.class/instance/doits/reprimeRegistryIssue197.st R BaselineOfMetacello.package/BaselineOfMetacello.class/instance/doits/testResourcePostLoadDoIt.st M Collections-Strings.package/String.class/instance/converting/subStrings_.st M Kernel.package/DeepCopier.class/definition.st M Kernel.package/DeepCopier.class/instance/like fullCopy/checkClass_.st M Kernel.package/DeepCopier.class/instance/like fullCopy/checkVariables.st R Kernel.package/DeepCopier.class/instance/like fullCopy/intervalForChecks.st R Kernel.package/DeepCopier.class/instance/like fullCopy/isItTimeToCheckVariables.st A Kernel.package/DeepCopier.class/instance/like fullCopy/warnInstanceVariableNotCopiedIn_selector_.st R Kernel.package/DeepCopier.class/instance/like fullCopy/warnIverNotCopiedIn_sel_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script178.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30523.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Support.package/SystemNavigation.class/instance/query/obsoleteMethodReferences.st M Tools.package/extension/SystemNavigation/instance/browseObsoleteReferences.st Log Message: ----------- 30523 12001 moved some isKindOf: to isXXX https://pharo.fogbugz.com/f/cases/12001 12004 delete empty packages https://pharo.fogbugz.com/f/cases/12004 12002 DeepCopier>>isItTimeToCheckVariables is candidate to be removed https://pharo.fogbugz.com/f/cases/12002 12005 unload BaselineOfFileTree, BaselineOfMetacello https://pharo.fogbugz.com/f/cases/12005 http://files.pharo.org/image/30/30523.zip

Oct. 25, 2013