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

declareTempAndPaste:

by Alexandre Bergel

Hi! Many of us have discovered that in the last Pharo adding a temporary variable is added before the | .. | part of the section. Pablo Estefo and I spend time on understanding where this comes from. But since this is deep into the compilation chain, it would be great if an expert (Marcus ? :-) could check what we have done. OCUndeclaredVariableWarning>>declareTempAndPaste: is the culprit method. We have changed: tempsMark := self methodNode body leftBar ifNil: [ self methodNode body start ]. into tempsMark := self methodNode body rightBar ifNil: [ self methodNode body start ]. So, the new version of the method should be: -=-=-=-=-=-=-=-=-=-=-=-= OCUndeclaredVariableWarning>>declareTempAndPaste: name | insertion delta theTextString characterBeforeMark tempsMark | theTextString := self methodNode source. tempsMark := self methodNode body rightBar ifNil: [ self methodNode body start ]. characterBeforeMark := theTextString at: tempsMark-1 ifAbsent: [$ ]. (theTextString at: tempsMark) = $| ifTrue: [ "Paste it before the second vertical bar" insertion := name, ' '. characterBeforeMark isSeparator ifFalse: [insertion := ' ', insertion]. delta := 0. ] ifFalse: [ "No bars - insert some with CR, tab" insertion := '| ' , name , ' |',String cr. delta := 2. "the bar and CR" characterBeforeMark = Character tab ifTrue: [ insertion := insertion , String tab. delta := delta + 1. "the tab" ] ]. tempsMark := tempsMark + (self substituteWord: insertion wordInterval: (tempsMark to: tempsMark-1) offset: 0) - delta. self methodNode scope addTemp: name. ^ (node owningScope lookupVar: node name) ifNil: [self error: 'should not happen'] -=-=-=-=-=-=-=-=-=-=-=-= We have tried different cases and it seems to work. Does this makes sense? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 11, 2013

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

by Camillo Bruni

On 2013-11-11, at 14:19, NicolÃ¡s Papagna Maldonado <nicolas.papagna(a)gmail.com> wrote: > Hi all! > > I've been working in a fix of PharoFilesOpener and decided to test the current behavior first before changing it, so I extracted the dependency to FileSystem and tried to use an instance created through FileSystem memory for testing. > > The code gets the write stream for a file and then sends the #isReadOnly message to do some stuff. > > The thing is that the streams returned form the in-memory file system are instances of WriteStream (see MemoryHandle >> writeStream) instead of StandardFileStream (see FileHandle >> writeStream) and so they don't respond the #isReadOnly message. > > Is this the expected way the in-memory file system should work? Shouldn't it return polymorphic file streams? You are absolutely right, it definitely should, but this requires a bit of work (see below) > If this is a bug, what change would you recommend to do? > I was thinking about returning StandardFileStreams instances from MemoryHandle >> writeStream. The memory filesystem works by definition in the image, whereas the StandardFileStream is bound to external file operations through the primitives (see for instance #basicNext). I think you have two choices here: 1. rewrite your code that it does not rely on the #isReadOnly but rather check up front if you can read the file 2. implement your own proper FileStream that works on the internal ByteArray of the memory FileSystem (maybe there is already a decent solution somewhere in the Zinc code) or of course, you start looking at porting XStreams to pharo ;), which on the long run will solve many more problems. The current situation is not that satisfactory :/

Nov. 11, 2013

Re: [Pharo-dev] Who is Penelope, Ulysse's wife?

by Benjamin

Penelope was the monkey used to migrate from Google issue tracker to fogbugz :) Ben On 11 Nov 2013, at 14:04, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Looks like to be a robot, but apparently she is able to fill bug entries? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Nov. 11, 2013

In-memory FileSystem write streams not being polymorphic

by NicolÃ¡s Papagna Maldonado

Hi all! I've been working in a fix of PharoFilesOpener and decided to test the current behavior first before changing it, so I extracted the dependency to FileSystem and tried to use an instance created through FileSystem memory for testing. The code gets the write stream for a file and then sends the #isReadOnly message to do some stuff. The thing is that the streams returned form the in-memory file system are instances of WriteStream (see MemoryHandle >> writeStream) instead of StandardFileStream (see FileHandle >> writeStream) and so they don't respond the #isReadOnly message. Is this the expected way the in-memory file system should work? Shouldn't it return polymorphic file streams? If this is a bug, what change would you recommend to do? I was thinking about returning StandardFileStreams instances from MemoryHandle >> writeStream. Cheers! Nico PM

Nov. 11, 2013

Who is Penelope, Ulysse's wife?

by Alexandre Bergel

Looks like to be a robot, but apparently she is able to fill bug entries? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 11, 2013

Contributor in Pharo30Inbox

by Alexandre Bergel

Hi! Someone can add "abergel" to the contributors please? http://smalltalkhub.com/#!/~Pharo/Pharo30Inbox/contributors Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 11, 2013

Re: [Pharo-dev] Bugs and files sites down?

by Max Leske

pharo.fogbugz.com is still online though. On 11.11.2013, at 13:47, Max Leske <maxleske(a)gmail.com> wrote: > I just forwarded the INRIA announcement to the list: due to maintenance files.pharo.org and get.pharo.org will remain down for the day. > > Max > > > On 11.11.2013, at 13:36, Pablo EstefÃ³ <pestefo(a)gmail.com> wrote: > >> Hi guys, >> >> We are trying to start the Pharo Sprint here at DCC UChile but the sites files.pharo.org / bugs.pharo.org seems to be down. >> >> Cheers, >> >> Pablo >

Nov. 11, 2013

Re: [Pharo-dev] Bugs and files sites down?

by Max Leske

I just forwarded the INRIA announcement to the list: due to maintenance files.pharo.org and get.pharo.org will remain down for the day. Max On 11.11.2013, at 13:36, Pablo EstefÃ³ <pestefo(a)gmail.com> wrote: > Hi guys, > > We are trying to start the Pharo Sprint here at DCC UChile but the sites files.pharo.org / bugs.pharo.org seems to be down. > > Cheers, > > Pablo

Nov. 11, 2013

Fwd: [ci-announces] CI shutdown on the 11th of November

by Max Leske

files.pharo.org and get.pharo.org will remain DOWN for the rest of the day. Begin forwarded message: > From: Emmanuel Jeanvoine <emmanuel.jeanvoine(a)inria.fr> > Subject: Re: [ci-announces] CI shutdown on the 11th of November > Date: 9. November 2013 09:00:31 MEZ > To: ci-announces(a)inria.fr > Reply-To: Emmanuel Jeanvoine <emmanuel.jeanvoine(a)inria.fr> > > On Thu, 07 Nov 2013, Emmanuel Jeanvoine wrote: > >> Dear users, >> >> The 11th of November, the IT department will stop the national IT >> services. As a consequence, the CI service will be stopped. >> >> In order to prevent any trouble, we strongly advice users to perform >> the following steps before the 11th of November (Sunday evening at the >> very latest): >> - stop the Jenkins instance of your project (see >> https://ci.inria.fr/project/PROJECTNAME/show#ci) >> - stop all the slaves related to your project (directly with a clean >> shutdown in the slave or from >> https://ci.inria.fr/project/PROJECTNAME/show#slaves) >> >> By the way, if you notice unused slaves in your project, you are >> strongly encouraged to removed them ("delete" button on >> https://ci.inria.fr/project/PROJECTNAME/show#slaves, or "destroy" >> button directly on the CloudStack interface). Stopping the unused >> slaves is not enough to free the related resources. >> >> Monday in the morning, the remaining running slaves will be stopped. >> After the maintenance, the Jenkins instances and the slaves will be >> restarted. >> >> Thus we hope that the service will be fully available on Tuesday in >> the morning. Anyway, since it is an heavy operation (major changes on >> the network of the datacenter) issues might occur, so we will >> communicate if communication means are available ;). >> >> Thank you for your understanding, >> Emmanuel > > > This is a reminder, you still have the opportunity to shutdown your > slaves and jenkins instances before tomorrow evening. This might be > useful to prevent slaves and jenkins corruption. > > Regards, > Emmanuel

Nov. 11, 2013

Bugs and files sites down?

by Pablo EstefÃ³

Hi guys, We are trying to start the Pharo Sprint here at DCC UChile but the sites files.pharo.org / bugs.pharo.org seems to be down. Cheers, Pablo

Nov. 11, 2013