- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [squeak-dev] Re: Process-specific state broken and uncomplete
by Igor Stasenko Nov. 9, 2010

Nov. 9, 2010

On 9 November 2010 05:59, Levente Uzonyi <leves(a)elte.hu> wrote: > On Tue, 9 Nov 2010, Igor Stasenko wrote: > > snip > >> Suppose you have a domain object which provides following ways to >> access the session: >> >> session: forkedSession >> Â Processor activeProcess environmentAt: #session put: forkedSession >> >> session >> Â ^ Processor activeProcess environmentAt: #session >> >> >> now, here what i'd like to write: >> >> | session | >> >> session := MySession new . >> session initialize blabla. >> >> "good fork" >> good := [ >> Â self session: session. >> Â [ self process stuff ] ensure: [ session close ] >> ] newProcess. >> >> good resume. >> 1 minute asDelay wait. >> good terminate. >> self assert: (session isClosed). >> >> In the above case, everything is ok: session object is passed in 'session' >> temp >> and visible inside ensure block directly, so, no matter what may >> happen (process termination), >> it is guaranteed that session will be closed at the end. >> >> "bad fork" >> >> session := MySession new . >> session initialize blabla. >> >> bad := [ >> Â self session: session. >> Â [ self process stuff ] ensure: [ self session close ] >> ] newProcess. >> >> bad resume. >> 1 minute asDelay wait. >> bad terminate. >> self assert: (session isClosed). >> >> >> In this case, a session is accessed indirectly, through process specific >> state. >> And test might fail or not, depending if process was already >> terminated before sending #terminate, >> or its still running. >> >> The 'bad fork' illustrates that one should not attempt to access a >> process specific state in ensure blocks, >> because during process termination, stack unwinding is performed by >> other process, which could have different session object, >> or don't have it at all. >> >> This is simple, of course, to implement session finalization without >> using process spefic state. But now consider that session has not only >> #close method, but allows doing something more userful, like: >> >> self session backupStuff. >> [ Â .. do something.. ] ensure: [ self session restoreStuff ]. >> >> And again, same problem: unless you have a direct reference to session >> object, you can't do it. >> Not with using process-specific state, because it is flawed. >> >> In other words, anything which may want to access to a >> process-specific state, like: >> >> [ ... ... ] ensure: [ (Processor activeProcess environmentAt: #foo) >> doSomething ] >> >> have no guarantees to work correctly in all cases. >> >> This defeats a purpose of process-specific state, because you can't >> rely on it for building a reliable stuff. > > Not really. You can store the sessions in a session store which is > responsible for retrieving the session: > > [ > Â Â Â Â sessionStore useSession: sessionKey during: [ :session | > Â Â Â Â Â Â Â Â Processor activeProcess environmentAt: #session put: session. > Â Â Â Â Â Â Â Â self doSomething. > Â Â Â Â Â Â Â Â Processor activeProcess environmentAt: #session put: nil ] ] > fork. > > SessionStore >> useSession: sessionKey during: aBlock > > Â Â Â Â | session | > Â Â Â Â [ > Â Â Â Â Â Â Â Â session := self sessionFor: sessionKey. > Â Â Â Â Â Â Â Â aBlock value: session ] > Â Â Â Â Â Â Â Â ensure: [ > Â Â Â Â Â Â Â Â Â Â Â Â session ifNotNil: [ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self releaseSession: session ] ] > > In #doSomething you can access the session via the process. We're using this > pattern in PostgresV3's connection pool. It works pretty well. > No, you can't. I feel sorry for you :) A #useSession:during: using ensure, and of course it will work correctly, because you not accessing session via process-specific storage. This is illustrated by my "good fork" example. now replace #doSomething with this: [ 1 year asDelay wait ] ensure: [ self assert: (Processor activeProcess environmentAt: #session) notNil ] and then terminate a process which running your fork. In attachment you'll find a test, which shows the problem (i using tests from Pharo image). > > Levente > > > snip > > -- Best regards, Igor Stasenko AKA sig.

2 2

[Pharo-project] about tracker activities
by StÃ©phane Ducasse Nov. 8, 2010

Nov. 8, 2010

Hi guys I think that we are not looking to the issues because we do not know that they have been entered. In the google web site we can special a mailing-list Activity notifications Email notifications of issue tracker activity will automatically be sent to the following email address. All issue changes: Notifications will be sent from: pharo(a)googlecode.com You may need to add this address as an allowed poster to your mailing list. If using Google Groups, add the address directly with no email delivery. And I would like to activate that. I hope that this is ok for you. People not interested can just add a filter to discard those mails. Marcus do you have an idea how we can make sure that the mails sent are not blocked? Stef

4 4

[Pharo-project] update issues template in google code [was] Re: about tracker activities
by Mariano Martinez Peck Nov. 8, 2010

Nov. 8, 2010

On Mon, Nov 8, 2010 at 6:52 PM, Stefan Marr <pharo(a)stefan-marr.de> wrote: > Hi: > > On 08 Nov 2010, at 22:06, StÃ©phane Ducasse wrote: > > > I think that we are not looking to the issues because we do not know that > they have been entered. > Bye the way, your issue reporting template needs an update. It contains > outdated information, i.e., that you are currently working on Pharo 1.1. > grrrr I don't remember how to do that? anyone? > > Best regards > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr <http://soft.vub.ac.be/%7Esmarr> > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > >

1 0

[Pharo-project] how to know if an image is resuming or not
by StÃ©phane Ducasse Nov. 8, 2010

Nov. 8, 2010

hi guys I'm too dead to think more but I want to do the following save the current image (I used saveSession) and only when not resuming I want to save another image. Is there a way to know if an image is resuming (if the pc pointer just go reactivated - that the image was closed and reopened). naively I was doing saveImageForRunningTests | comment commentQuoted st | SmalltalkImage current saveSession. "now you can reopen prior to publishing to fix :)" self saveAsImageAsTestImage. self inform: 'Now you can use this image named ''Test'' to run the tests and come back to fix problems in the previous one and eventually freeze it by selecting the next step, in either one.' and of course when I reopened the save session I reperformed the "self saveAsImageAsTestImage." Now I could use startUp:.... Or I could simply change my process but I wanted to know... I'm too dead now. Stef

2 1

Re: [Pharo-project] about consistency between hex implementations
by StÃ©phane Ducasse Nov. 8, 2010

Nov. 8, 2010

On Nov 8, 2010, at 10:39 PM, Eliot Miranda wrote: > > > On Mon, Nov 8, 2010 at 1:22 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> > >> > >> in pharo we have > >> hex that always returns 16rXX > >> > >> $A hex '16r41' > >> > >> 20 hex '16r14' > >> > >> Even if this is regular this is not really nice. In fact this ones should be fixed to return numbers and not strings. > >> I do not understand why hex should return a string. > > > > And how? Integer >> #hex would be ^self and Character >> #hex would be ^value ? > > It looks like I proposed something stupid :) you are right we cannot generate 16r41 as a number. I was sure that we could do that so that I do not even check. > This is strange that we cannot generate these numbers. This is strange to have things that we can only parse but not generate other than via strings. > We could have something like Integer value: 65 base: 16 that returns 16r41 and not 65 and not '16r41' > When I type 16r41 my mental perception is not that this is a string but this is a number I'm manipulating. > Like #foo, true,.... I do not think in terms of strings just objects. Now for true, #foo this is simpler because they only have one representation. > Now the fact that several objects denotes the same elementary element is just an accident. So this was fun that I could think that :). > > > Now my post had two topics and I would like at least to get the other fixed: consistency. > > $A hex '16r41' > > 20 hex '16r14' > > $A printStringHex > '41' > 20 printStringHex > '14' > > +1. The above definitions of hex are what VMMaker wants. Ok I will send you a cs for squeak! Now I'm fighting with MC on something else (instead of writing a nice letter for a Phd evaluation :) > > Stef >

1 0

Re: [Pharo-project] about tracker activities
by StÃ©phane Ducasse Nov. 8, 2010

Nov. 8, 2010

Thanks! On Nov 8, 2010, at 10:53 PM, Stefan Marr wrote: > Hi: > > On 08 Nov 2010, at 22:06, StÃ©phane Ducasse wrote: > >> I think that we are not looking to the issues because we do not know that they have been entered. > Bye the way, your issue reporting template needs an update. It contains outdated information, i.e., that you are currently working on Pharo 1.1. > > Best regards > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > >

1 0

Re: [Pharo-project] about consistency between hex implementations
by StÃ©phane Ducasse Nov. 8, 2010

Nov. 8, 2010

>> >> >> in pharo we have >> hex that always returns 16rXX >> >> $A hex '16r41' >> >> 20 hex '16r14' >> >> Even if this is regular this is not really nice. In fact this ones should be fixed to return numbers and not strings. >> I do not understand why hex should return a string. > > And how? Integer >> #hex would be ^self and Character >> #hex would be ^value ? It looks like I proposed something stupid :) you are right we cannot generate 16r41 as a number. I was sure that we could do that so that I do not even check. This is strange that we cannot generate these numbers. This is strange to have things that we can only parse but not generate other than via strings. We could have something like Integer value: 65 base: 16 that returns 16r41 and not 65 and not '16r41' When I type 16r41 my mental perception is not that this is a string but this is a number I'm manipulating. Like #foo, true,.... I do not think in terms of strings just objects. Now for true, #foo this is simpler because they only have one representation. Now the fact that several objects denotes the same elementary element is just an accident. So this was fun that I could think that :). Now my post had two topics and I would like at least to get the other fixed: consistency. $A hex '16r41' 20 hex '16r14' $A printStringHex '41' 20 printStringHex '14' Stef

3 2

[Pharo-project] about consistency between hex implementations
by stephane ducasse Nov. 8, 2010

Nov. 8, 2010

Hi eliot I was going over some changes and I noticed that in squeak 20 hex 16r41 $A hex '41' in pharo we have hex that always returns 16rXX $A hex '16r41' 20 hex '16r14' Even if this is regular this is not really nice. In fact this ones should be fixed to return numbers and not strings. I do not understand why hex should return a string. and in pharo printStringHex the XX part only $A printStringHex '41' 20 printStringHex '14' Here this is a string since the name says it. In VW there is asHexString which is nice too. So could we agree on that and get a system that is nicer and more consistent. Stef

2 1

Nov. 8, 2010

On Nov 8, 2010, at 6:21 PM, nullPointer wrote: > > For a TIP example I want implement in Pharo the steps for build a GUI like > that: > > http://forum.world.st/file/n3032341/eBox.png gorgeous! > The main problem for me is the window style. I understand one way for change > the style of windows is create my own UITheme subclass; but exists some > alternative way for generate a new style for windows? a generic window: I > only want a one panel with the three buttons for close, minimize and > maximize, and the rounded corners, much more rebranded in top corners than > bottom, with the default behavior of window: draggable for the Desktop. I do not know. > Perhaps the best way for implement it is know if is possible change a few > properties of a panel for have the same behavior of a window. > > Many thanks for the help. > -- > View this message in context: http://forum.world.st/Best-way-for-change-a-window-style-tp3032341p3032341.… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

2 1

[Pharo-project] Monticello in Squeak 3.7 MVC-only Or changeset updater script?
by Stefan Marr Nov. 8, 2010

Nov. 8, 2010

Hi: Does anyone know (perhaps Dale?) how likely it is to get Monticello in a MVC-only image running? I checked the documentation at http://www.wiresong.ca/monticello/v1/docs/getting-started.html and the update IDs seem to be ok. At least my image identifies it self with 'latest update: #5959'. (thats the image: https://github.com/downloads/smarr/RoarVM/minimal-MVC.zip) However, neither the document, nor SqueakMap give me the feeling that I actually know how to start loading it. I found http://ftp.squeak.org/3.11-obsolete/scripts/mc15.st but well, thought I ask here first. If that does not seem to feasible, does anyone know a ready-to-use script to build a change set from a number of Monticello packages automatically taking dependencies into account? Would be nice, if I could hook something into the package saving mechanism that spills out an updated .st file every time I safe a package. Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

2 3