June 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] How to migrate an object to a subclass of its class but with new inst vars ?

by Blondeau Vincent

Hi, You should be able to do it using the method primitiveChangeClassTo: but it not recommended to do it. Are you sure that it is the only way to resolve your problem? If you really want to, an example: Object subclass: #Toto slots: { #tata } classVariables: { } category: 'Temp'. Toto subclass: #Titi slots: { } classVariables: { } category: 'Temp'. obj := Toto new. obj primitiveChangeClassTo: Titi new. obj has a new class. However, you cannot add a new instance variable this way but you keep the values of the instance. But nothing avoid you to add an empty instance variable in a superclass that only the subclass will use. I hope that it will help you Vincent De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de Steven Costiou EnvoyÃ© : mercredi 7 juin 2017 14:54 Ã : Pharo users users Objet : [Pharo-users] How to migrate an object to a subclass of its class but with new inst vars ? Hi, i'm trying to migrate an object from a given class A to a subclass of A with new inst vars. Can't get it to work. I have a class and an instance of it, say: Object subclass: #A instanceVariableNames: '' |a| a := A new. A has no instance variables. Now i create a subclass B of A with a new inst var: A subclass: #B instanceVariableNames: 'x' I want to do the following: B adoptInstance: a It does'nt work, for what i understand it is because the format of the classes are different (B has an inst var and A has not). How can i make the a object become an instance of B (subclass of a's class), making a acquiring the new inst var x (and in more complex cases keeping its own previous inst vars) ? Steven. !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

June 7, 2017

How to migrate an object to a subclass of its class but with new inst vars ?

by Steven Costiou

Hi, i'm trying to migrate an object from a given class A to a subclass of A with new inst vars. Can't get it to work. I have a class and an instance of it, say: Object subclass: #A instanceVariableNames: '' |a| a := A new. A has no instance variables. Now i create a subclass B of A with a new inst var: A subclass: #B instanceVariableNames: 'x' I want to do the following: B adoptInstance: a It does'nt work, for what i understand it is because the format of the classes are different (B has an inst var and A has not). How can i make the a object become an instance of B (subclass of a's class), making a acquiring the new inst var x (and in more complex cases keeping its own previous inst vars) ? Steven.

June 7, 2017

Re: [Pharo-users] [ANN] Pharo 6.0 released!

by Pierce Ng

On Tue, Jun 06, 2017 at 05:11:17PM +0200, Esteban Lorenzano wrote: > The time has come for Pharo 6.0! Fantastic! Congrats and thanks for all the hard work. Pierce

June 7, 2017

Re: [Pharo-users] rewrite question

by werner kassens

On 06/07/2017 12:46 PM, werner kassens wrote: > Hi, > > where do i find the 'rewrite tool' described in the paper 'Code > Transformation by Direct Transformation of ASTs' by Rizun et al? > > werner > > > oops, found it, i read the paper a bit too fast, sorry. werner

June 7, 2017

rewrite question

by werner kassens

Hi, where do i find the 'rewrite tool' described in the paper 'Code Transformation by Direct Transformation of ASTs' by Rizun et al? werner

June 7, 2017

Re: [Pharo-users] Some Metacello issue

by Holger Freyther

> On 7. Jun 2017, at 14:09, Stephan Eggermont <stephan(a)stack.nl> wrote: > > Never refer to fixed versions unless you know why (you need to avoid a > specific bug fix). When wanting to have repeatable builds (e.g. for bugfixes) and in the absence of other means to lock/define versions externally, I think using a fixed version is the way to go. > What is most likely is that there is some overconstrained configuration. > Does your ConfigurationOfVoyageMongo or one of the configurations it > pulls in refer to different versions of grease or magritte? Another > issue can be that there are older configurations already loaded that > conflict with the newest ones. Indeed, the ConfigurationOfMongoTalk > is broken, refering to a fixed and older version of Grease. > ConfigurationOfVoyageMongo should probably be using #'release3' of > Magritte, but that doesn't break it. Right. So we have a "OsmocomUniverse" build job that pulls in all the apps into a single image. This helps to make API modifications and not forget any of the client code. The configuration has such dependencies: ConfigurationOfOsmocomUniverse -> ConfigurationOfHLR -> ConfigurationOfVoyageMongo -> Mongotalk -> Grease A -> Magritte3 -> Grease B -> ConfigurationOfSMPPRouter -> ConfigurationOfVoyageMongo -> Mongotalk -> Grease A -> Magritte3 -> Grease B What happens is that somehow "Grease A" gets loaded, then "Grease B" and when it is time for "Grease A" again.. the system kind of explodes and this is for Pharo3 and Pharo6. Now the question to me is.. why is this coming up right now? Did MongoTalk change or Magritte3 or something else? Is there an easy way for Metacello to try a mirror instead of the original, e.g. to inject an older ConfigurationOfMagritte3? holger

June 7, 2017

Re: [Pharo-users] Porting Transducers to Pharo

by phil＠highoctane.be

Use Iceberg with Pharo6.0 There are techtalks videos about it. https://www.youtube.com/watch?v=AuZAFfWS34w&t=29s Phil On Wed, Jun 7, 2017 at 11:29 AM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: > Hi Phil, > > that's great. I do have a GitHub account (merkste) but none at > SmalltalkHub. Is there a recommendable doc on how to use Git from Pharo? > > Best, Steffen > > > > Am .06.2017, 14:09 Uhr, schrieb phil(a)highoctane.be <phil(a)highoctane.be>: > > Hi Steffen, >> >> I am willing to help you create the package in SmalltalkHub or Github >> based >> on your files/changeset. >> >> Do you have a github and/or SmalltalkHub account? >> >> Best, >> Phil >> >> >> On Tue, Jun 6, 2017 at 1:08 PM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: >> >> Hi! >>> >>> If the need arises, we could of course factor the compact notation out >>> into >>> >>>> a separate package. >>>>> >>>>> Good idea >>>> [...] I do not want to help promoting a syntax that alienates me (and >>>> others because other people reported the saem to me). >>>> >>>> >>> I understand. Btw, I'd really, really appreciate if others post their >>> thoughts and feedback here as well. Discussion helps moving things >>> forward. >>> =) >>> >>> >>> (collection transduce map: #squared) take: 1000. >>> >>>> >>>>> >>>> To me this is much more readable. >>>> >>>> >>> Well, I'll provide that extension once it is finished. >>> >>> I cannot and do not want to use the other forms. >>> >>>> >>>> >>> >>> collection transduce >>> >>>> map: #squared; >>>>> take: 1000. >>>>> >>>>> But as the message chain has to modify the underlying object >>>>> (an eduction), very snaky side effects my occur. E.g., consider >>>>> >>>>> eduction := collection transduce. >>>>> squared := eduction map: #squared. >>>>> take := squared take: 1000. >>>>> >>>>> Now, all three variables hold onto the same object, which first squares >>>>> all elements and than takes the first 1000. >>>>> >>>>> >>>> This is because the programmer did not understand what he did. No? >>>> >>>> >>> Sure. ;-) Nevertheless, it would be very hard to debug. All of which are >>> the reasons I wouldn't implement that variant. ;-) >>> >>> >>> PS: I played with infinite stream and iteration back in 1993 in CLOS. >>> >>>> Now I do not like to mix things because it breaks my flow of thinking. >>>> >>>> >>> >>> I am not sure whether I understand what your mean by mixing. Concerning >>> transducers, the ability to handle infinite sources in only a (natural) >>> side-effect of the ability to finish reductions before all elements are >>> processed, e.g., like #detect: and such. >>> >>> Best, Steffen >>> >>> >>> >>> >>> >>> > >

June 7, 2017

Re: [Pharo-users] Porting Transducers to Pharo

by Damien Pollet

I wouldn't bother with SmalltalkHub at this point. Check Iceberg, it's the future: https://github.com/pharo-vcs/iceberg/ On 7 June 2017 at 11:29, Steffen MÃ¤rcker <merkste(a)web.de> wrote: > Hi Phil, > > that's great. I do have a GitHub account (merkste) but none at > SmalltalkHub. Is there a recommendable doc on how to use Git from Pharo? > > Best, Steffen > > > > > Am .06.2017, 14:09 Uhr, schrieb phil(a)highoctane.be <phil(a)highoctane.be>: > > Hi Steffen, >> >> I am willing to help you create the package in SmalltalkHub or Github >> based >> on your files/changeset. >> >> Do you have a github and/or SmalltalkHub account? >> >> Best, >> Phil >> >> >> On Tue, Jun 6, 2017 at 1:08 PM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: >> >> Hi! >>> >>> If the need arises, we could of course factor the compact notation out >>> into >>> >>>> a separate package. >>>>> >>>>> Good idea >>>> [...] I do not want to help promoting a syntax that alienates me (and >>>> others because other people reported the saem to me). >>>> >>>> >>> I understand. Btw, I'd really, really appreciate if others post their >>> thoughts and feedback here as well. Discussion helps moving things >>> forward. >>> =) >>> >>> >>> (collection transduce map: #squared) take: 1000. >>> >>>> >>>>> >>>> To me this is much more readable. >>>> >>>> >>> Well, I'll provide that extension once it is finished. >>> >>> I cannot and do not want to use the other forms. >>> >>>> >>>> >>> >>> collection transduce >>> >>>> map: #squared; >>>>> take: 1000. >>>>> >>>>> But as the message chain has to modify the underlying object >>>>> (an eduction), very snaky side effects my occur. E.g., consider >>>>> >>>>> eduction := collection transduce. >>>>> squared := eduction map: #squared. >>>>> take := squared take: 1000. >>>>> >>>>> Now, all three variables hold onto the same object, which first squares >>>>> all elements and than takes the first 1000. >>>>> >>>>> >>>> This is because the programmer did not understand what he did. No? >>>> >>>> >>> Sure. ;-) Nevertheless, it would be very hard to debug. All of which are >>> the reasons I wouldn't implement that variant. ;-) >>> >>> >>> PS: I played with infinite stream and iteration back in 1993 in CLOS. >>> >>>> Now I do not like to mix things because it breaks my flow of thinking. >>>> >>>> >>> >>> I am not sure whether I understand what your mean by mixing. Concerning >>> transducers, the ability to handle infinite sources in only a (natural) >>> side-effect of the ability to finish reductions before all elements are >>> processed, e.g., like #detect: and such. >>> >>> Best, Steffen >>> >>> >>> >>> >>> >>> >

June 7, 2017

Re: [Pharo-users] Porting Transducers to Pharo

by Steffen MÃ¤rcker

Hi Phil, that's great. I do have a GitHub account (merkste) but none at SmalltalkHub. Is there a recommendable doc on how to use Git from Pharo? Best, Steffen Am .06.2017, 14:09 Uhr, schrieb phil(a)highoctane.be <phil(a)highoctane.be>: > Hi Steffen, > > I am willing to help you create the package in SmalltalkHub or Github > based > on your files/changeset. > > Do you have a github and/or SmalltalkHub account? > > Best, > Phil > > > On Tue, Jun 6, 2017 at 1:08 PM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: > >> Hi! >> >> If the need arises, we could of course factor the compact notation out >> into >>>> a separate package. >>>> >>> Good idea >>> [...] I do not want to help promoting a syntax that alienates me (and >>> others because other people reported the saem to me). >>> >> >> I understand. Btw, I'd really, really appreciate if others post their >> thoughts and feedback here as well. Discussion helps moving things >> forward. >> =) >> >> >> (collection transduce map: #squared) take: 1000. >>>> >>> >>> To me this is much more readable. >>> >> >> Well, I'll provide that extension once it is finished. >> >> I cannot and do not want to use the other forms. >>> >> >> >> collection transduce >>>> map: #squared; >>>> take: 1000. >>>> >>>> But as the message chain has to modify the underlying object >>>> (an eduction), very snaky side effects my occur. E.g., consider >>>> >>>> eduction := collection transduce. >>>> squared := eduction map: #squared. >>>> take := squared take: 1000. >>>> >>>> Now, all three variables hold onto the same object, which first >>>> squares >>>> all elements and than takes the first 1000. >>>> >>> >>> This is because the programmer did not understand what he did. No? >>> >> >> Sure. ;-) Nevertheless, it would be very hard to debug. All of which are >> the reasons I wouldn't implement that variant. ;-) >> >> >> PS: I played with infinite stream and iteration back in 1993 in CLOS. >>> Now I do not like to mix things because it breaks my flow of thinking. >>> >> >> >> I am not sure whether I understand what your mean by mixing. Concerning >> transducers, the ability to handle infinite sources in only a (natural) >> side-effect of the ability to finish reductions before all elements are >> processed, e.g., like #detect: and such. >> >> Best, Steffen >> >> >> >> >>

June 7, 2017

Re: [Pharo-users] How to deploy headless app without changes and source files?

by Sven Van Caekenberghe

> On 7 Jun 2017, at 09:38, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I think that could/would work (the code in System-Sources was refactored quite well). I added an issue and a slice (in the Pharo 6 inbox): https://pharo.fogbugz.com/f/cases/20126/Running-Without-Changes-and-Sources Make it possible to Run without changes and sources Add two new classes: - NoChangesLog as subclass of ChangesLog - NoPharoFilesOpener as subclass of PharoFilesOpener Both are do nothing variants of their superclass. To run without changes or sources, execute NoChangesLog install. NoPharoFilesOpener install. And save your image. You now no longer need the changes file nor the sources file and you can safely move or remove them. To restore the initial situation, execute ChangesLog reset. PharoFilesOpener reset. Note: it might be possible that some code fails due to missing method sources, YMMV. Warning: of course you should no longer develop in such an image. Sven

June 7, 2017