June 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] FileReference should throw error when deleting unexisting files?

by Chris Cunningham

On Mon, Jun 11, 2012 at 2:32 PM, <petton.nicolas(a)gmail.com> wrote: > Maybe #ensureDeleted would be better? > > Nico I like #ensureDeleted (make sure it doesn't exist)

June 11, 2012

Re: [Pharo-project] FileReference should throw error when deleting unexisting files?

by petton.nicolas＠gmail.com

Mariano Martinez Peck <marianopeck(a)gmail.com> writes: > On Mon, Jun 11, 2012 at 8:38 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: > > So if we now do: > > Â 'afileThatDoesntExist' asFileReference delete > > I get a PrimitiveFailed. If this is what we want, can I add: > > FileReference >> deleteIfExists > > > self exists ifTrue: [ self delete] > > > > > So I discussed in IRC and Camillo and Sean recommended to use > #ensureDelete because it is concistent to ensureFile and > ensureDirecotry etc... > for me #ensureDelete sounds the opposite to what this method does > because I am not ensuring anything, if fact, I won't remove anything > if the file does not exist. I like #ensureDelete, because yes, it is consistent. I see it as "make sure the file is deleted", so it makes sense to me. Maybe #ensureDeleted would be better? Nico > Camilo also suggested to do > > > FileReference >> deleteIfExists > > self deleteIfAbsent: [ ] > > > FileReference >> deleteIfAbsent: aBlock > > self exists > Â Â Â Â Â ifTrue: [self delete] > Â Â Â Â Â ifFalse: [aBock value] > > > What do you think? which one do you like more?Â #ensureDelete or > #deleteIfExists?Â > do you also agree to add the intermediate #deleteIfAbsent:Â ? > > Cheers > > > Â > > or something like that?Â Â because lots of places (tearDown of > tests) I want to remove crao which may or may not exist... > > thanks > > -- > Mariano > http://marianopeck.wordpress.com -- Nicolas Petton http://nicolas-petton.fr

June 11, 2012

Re: [Pharo-project] recompiling class

by Sean P. DeNigris

StÃ©phane Ducasse wrote > > Soon we will be able to remove FileDirectory :) Yippppppppppie!!!!! -- View this message in context: http://forum.world.st/recompiling-class-tp4633989p4634388.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 11, 2012

Re: [Pharo-project] zip bug [IMPORTANT] probably related to the recent Zip changes

by StÃ©phane Ducasse

On Jun 11, 2012, at 3:47 AM, Sean P. DeNigris wrote: > so I'm refactoring blind!! Scary :) Yes I know that feelingâ¦.

June 11, 2012

Re: [Pharo-project] recompiling class

by StÃ©phane Ducasse

+ 1 and we are working on that :) Soon we will be able to remove FileDirectory :), will have Morph rendered in Athensâ¦. On Jun 11, 2012, at 9:45 AM, Tudor Girba wrote: > +1. > > It is in your interest to get us to move to the latest version, and > the best way to do it is to keep offering irresistible reasons :) > > Cheers, > Doru > > > On Mon, Jun 11, 2012 at 9:31 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On Jun 11, 2012, at 7:17 AM, S Krish wrote: >> >>> "decompile to an Intermediate Representation" >>> >>> This will be nice to have backported if possible to 1.4. >>> >> IR: you can do it. Whole compiler: no way, as it changes APIs >> and honestly, life is too short. >> >> Marcus >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

June 11, 2012

Re: [Pharo-project] Pharo 2.0 Jenkins build failing

by StÃ©phane Ducasse

Thanks Sean. I'm going to paris for a presentation so I may have a look tomorrow evening. Stef On Jun 11, 2012, at 6:33 PM, Sean P. DeNigris wrote: > Fix attached to: > Issue 6055: [BUG] New System Progress doesn't work when headless > http://code.google.com/p/pharo/issues/detail?id=6055 > > > >> 2.0 >> >> When headless and displaying progress, with used to be a no-op, now there >> is a BlockClosure DNU label:. This is because progress used to use a block >> that was pretending to be a class, so #value: would get sent everywhere, >> with the "selector" as the argument (e.g. value: #label). Now that we have >> a real progress object, we are sending #label: explicitly. Since >> CommandLineUIManager wasn't updated, it's still passing a block ([:bar >> |]), which obviously doesn't understand #label: >> >> The attached st files fix CommandLineUIManager to use a >> DummySystemProgressItem instead of a block. >> >> There will be more refactoring of the entire system progress framework, >> but let's get it working, one step at a time. >> >> N.B. The DummySystemProgressItem was temporarily placed in its own >> category to avoid making Morphic-Widgets dirty, which would be wiped out >> as the updates to 20119 are loaded >> > > -- > View this message in context: http://forum.world.st/Pharo-2-0-Jenkins-build-failing-tp4634306p4634339.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

June 11, 2012

[Pharo-project] 2.0

by Schwab,Wilhelm K

I grabbed the one-click image and poked around. The worst thing I found (can't reproduce) is that the SB's package list became insensitive to clicks. Switching to groups and then back seemed to restore normal operation. Looks good so far! Bill

June 11, 2012

Re: [Pharo-project] FileReference should throw error when deleting unexisting files?

by Mariano Martinez Peck

On Mon, Jun 11, 2012 at 8:38 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > So if we now do: > > 'afileThatDoesntExist' asFileReference delete > > I get a PrimitiveFailed. If this is what we want, can I add: > > FileReference >> deleteIfExists > > self exists ifTrue: [ self delete] > > So I discussed in IRC and Camillo and Sean recommended to use #ensureDelete because it is concistent to ensureFile and ensureDirecotry etc... for me #ensureDelete sounds the opposite to what this method does because I am not ensuring anything, if fact, I won't remove anything if the file does not exist. Camilo also suggested to do FileReference >> deleteIfExists self deleteIfAbsent: [ ] FileReference >> deleteIfAbsent: aBlock self exists ifTrue: [self delete] ifFalse: [aBock value] What do you think? which one do you like more? #ensureDelete or #deleteIfExists? do you also agree to add the intermediate #deleteIfAbsent: ? Cheers > or something like that? because lots of places (tearDown of tests) I > want to remove crao which may or may not exist... > > thanks > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

June 11, 2012

Re: [Pharo-project] FileReference >> #exists not working?

by Esteban Lorenzano

digging with Camillo in the code implementation and realizing that there was a bug in the plugin support files :) Esteban On Jun 11, 2012, at 8:49 PM, Sean P. DeNigris wrote: > > Sean P. DeNigris wrote >> >> * Issue 6050: ensureDirectory looks strange >> http://code.google.com/p/pharo/issues/detail?id=6050 >> > > The code snippet works now with the Jenkins Cog VM at > https://ci.lille.inria.fr/pharo/job/Cog-VM/ (build #45 - last successful) > > Good... that was a scary one. How was it resolved? > > -- > View this message in context: http://forum.world.st/FileReference-exists-not-working-tp4634285p4634359.ht… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

June 11, 2012

Re: [Pharo-project] FileReference >> #exists not working?

by Esteban Lorenzano

none :) (they should be not active, and removed soon) use this: https://ci.lille.inria.fr/pharo/view/Cog/job/Cog-VM/ Esteban On Jun 11, 2012, at 8:33 PM, Mariano Martinez Peck wrote: > > > On Mon, Jun 11, 2012 at 5:21 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > both were same problem and both *should* (not completely sure, he) work on latest vm, please check :) > > please, tell me EXACTLY which job. > https://ci.lille.inria.fr/pharo/view/VM-dev/ has 6 jobs. > https://ci.lille.inria.fr/pharo/view/Cog/ has 11 jobs > https://ci.lille.inria.fr/pharo/view/VM/ has 1 job. > > so...which one? > > > (if we can get jenkings to work again, :) > > > > On Jun 11, 2012, at 4:20 PM, Sean P. DeNigris wrote: > > > > > EstebanLM wrote > >> > >> can be related to http://code.google.com/p/pharo/issues/detail?id=5693 > >> > > > > That one was effecting symlinks. It's more probably related to... > > > > http://forum.world.st/FilePlugin-changed-it-s-behavior-td4633565.html > > There's something weird and scary going on with FilePlugin... > > * Issue 6050: ensureDirectory looks strange > > http://code.google.com/p/pharo/issues/detail?id=6050 > > * http://forum.world.st/FilePlugin-bug-td4634074.html > > > > -- > > View this message in context: http://forum.world.st/FileReference-exists-not-working-tp4634285p4634300.ht… > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com >

June 11, 2012