October 2013 - Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] DeepCopier>>isItTimeToCheckVariables

by Martin Dias

Reported: https://pharo.fogbugz.com/f/cases/12002/DeepCopier-isItTimeToCheckVariables… On Fri, Oct 25, 2013 at 12:57 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > > > Yes, this can be cleanup up. > > On 25 Oct 2013 at 11:10:34, Martin Dias (tinchodias(a)gmail.com<//tinchodias(a)gmail.com>) > wrote: > > Hi, > > This method in DeepCopier has no senders (in Pharo 3) and it's the only > who references the class variable NextVariableCheckTime. > > The time stamp says 1999... Unused code to remove? > > > isItTimeToCheckVariables > > | now isIt | > NextVariableCheckTime ifNil: [ > NextVariableCheckTime := Time totalSeconds. > ^ true]. > now := Time totalSeconds. > isIt := NextVariableCheckTime < now. > isIt ifTrue: ["update time for next check" > NextVariableCheckTime := now + self intervalForChecks]. > ^isIt > > > Cheers, > MartÃn > >

Oct. 25, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 25, 2013

[pharo-project/pharo-core] 30a35f: 30522

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 30a35f96d7a19a6c2d1c95ff359c2cdaa1dde9bf https://github.com/pharo-project/pharo-core/commit/30a35f96d7a19a6c2d1c95ff… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-25 (Fri, 25 Oct 2013) Changed paths: R Kernel.package/Behavior.class/instance/accessing/localSelectors.st R Kernel.package/Class.class/instance/accessing/localSelectors.st R Kernel.package/Metaclass.class/instance/accessing/localSelectors.st M KernelTests.package/ClassTest.class/instance/testing/testClassRespectsPolymorphismWithTrait.st M KernelTests.package/MetaclassTest.class/instance/tests/testMetaclassAndTraitClassRespectsPolymorphismRules.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script177.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30522.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Traits.package/TraitBehavior.class/instance/accessing/localSelectors.st Log Message: ----------- 30522 12000 localSelectors can be implemented in TBehavior https://pharo.fogbugz.com/f/cases/12000 http://files.pharo.org/image/30/30522.zip

Oct. 25, 2013

Re: [Pharo-dev] VM for Athens Graphics

by Igor Stasenko

On 25 October 2013 10:52, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 24.10.2013 um 12:51 schrieb Igor Stasenko <siguctua(a)gmail.com>: > > > > > On 24 October 2013 08:24, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> >> Am 23.10.2013 um 23:28 schrieb Igor Stasenko <siguctua(a)gmail.com>: >> >> >> >> >> On 23 October 2013 23:13, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: >> >>> >>>> >>> Well implementing ARM-FFI is largely orthogonal to Athens. >>> Yes, i am happily using it for Cairo and it lets me customize /rethink >>> things as they go >>> without need to touch VM. Which means much faster development process >>> and feedback etc. >>> But since Athens API is settled down more or less, now it is quite >>> possible to implement a plugin >>> for different backend, knowing that it won't require huge changes later. >>> >>> >>> Ok I was not aware you were thinking about that. So this is good to have >>> this path in my radar. >>> >>> Yes, this is actually what we discussed recently with Esteban about >> possible alternatives and >> low-hanging fruits :) >> >> >>> Concerning ARM: >>> - Damien Pollet works on ARM assembler for ASMJit. >>> as soon as it working, we can try doing something with it. >>> >>> But in addition, what i would like to do is to move more towards >>> platform-neutral FFI implementation, >>> using low-level assembler DSL which is platform neutral. There's a work >>> started on it >>> as part of Mate project, but it is yet far from finished. >>> >>> >>> I would love that. >>> Now I guess that I'm correct to say that even with it the fact that it >>> would generate assembly on the fly >>> would make it a no go for iPad and friends. >>> >>> I thought that esteban and you thought about generating the "assembly >>> once for all for Ipda and putting it in file" >>> so that we do not have the "assembly generation" problem? >>> >>> that's a big question, whether such idea fits into apple >> technicians/politicans heads or not. >> Do you think we have enough time/resources to waste on implementing such >> mechanism >> only to discover later that Apple says 'over my dead body'? >> The point is that generating code, saving it to file, and then loading >> that file as DLL, >> is largely a hack. >> You either allowed to run your own generated code or not.. because from >> security perspective, >> the fact that you first stored it into file and then load it back doesn't >> changes a tiny bit. >> >> >> You store the code in a file in order to rip off the code generation part >> from your image. That would make it comply to apples policies. Same goes >> for the compiler. You are also not allowed to download a library and use it >> in your program. I think the plot is that apps get examined before they are >> allowed to be in the appstore. Changing the runtime would break this >> certification of the binary and apple would loose control because everybody >> would add a clean binary to the examination process and then they would >> load everything else when the user opens the app for the first time. So >> there is some sense in this. It is just a different way of thinking that we >> find annoying. >> > The sense is that i'm not changing NativeBoost each time i using it, so i > am not "changing the runtime". > It is pure fallacy to consider code as something else than just simple > data. > Sure thing, if i mutate the codebase by loading external code from random > source later (and this is what we regularly do with our images) > then the contract is broken. But not in case when all my code and i'm not > changing it in any way. The fact it using code generation doesn't means it > will turn into something else if i don't want to. > > It is all about if you have the possibility to change the runtime at > runtime or not. If you put native code into a file and remove everything > that might change it you have the runtime apple wants. For me this is not > philosophical debate so I donât go into details. I donât even like coming > close to defend the way apple does it. Coming from the system side I just > have two hearts beating in my chest. The old one (the security/dark side) > tells me you have to restrict everything to be safe. The other/new one > tells me: Screw the dark side. Weâll get nowhere with this attitude, let us > invent stuff instead of fear stuff. > > Right. In any case, Apple is not the center of universe, and there's android which is much less restrictive. We need code generation for ARM CPU.. and FFI. Whether some OS does or not supports certain things is secondary to that. > Norbert > > > >> Norbert >> >> From design perspective, it is crutch, which don't really buys anything >> (why on earth, anyone would want to deal with files >> and OS, if he could just run code which already in memory?). >> >> > > > -- > Best regards, > Igor Stasenko. > > > -- Best regards, Igor Stasenko.

Oct. 25, 2013

Re: [Pharo-dev] DeepCopier>>isItTimeToCheckVariables

by Marcus Denker

Yes, this can be cleanup up. On 25 Oct 2013 at 11:10:34, Martin Dias (tinchodias(a)gmail.com) wrote: Hi, This method in DeepCopier has no senders (in Pharo 3) and it's the only who references the class variable NextVariableCheckTime. The time stamp says 1999... Unused code to remove? isItTimeToCheckVariables | now isIt | NextVariableCheckTime ifNil: [ NextVariableCheckTime := Time totalSeconds. ^ true]. now := Time totalSeconds. isIt := NextVariableCheckTime < now. isIt ifTrue: ["update time for next check" NextVariableCheckTime := now + self intervalForChecks]. ^isIt Cheers, MartÃn

Oct. 25, 2013