- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] VTermOutputDriver

by Max Leske

> On 11 Jul 2016, at 11:19, Valentin Ryckewaert <valentin.ryckewaert(a)gmail.com> wrote: > > The problem is that my class have an outStream which is nil, it shouldn't be the case, i'm searching why right now, you think it's your modification which did that? That might be the reason of the failure, but itâs not the reason for the stack trace :) > > 2016-07-11 11:15 GMT+02:00 Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: > This seems to be a bug in the fix I recently made to ImageWorker (althought the VTerm problem is another thingâ¦). Let me create a fix and Iâll get back to you. > > Cheers, > Max > > >> On 11 Jul 2016, at 10:48, Blondeau Vincent <vincent.blondeau(a)worldline.com <mailto:vincent.blondeau@worldline.com>> wrote: >> >> That is not the pointâ¦ Look at the end: >> >> MessageNotUnderstood: receiver of "nextPutAll:" is nil >> UndefinedObject(Object)>>doesNotUnderstand: #nextPutAll: >> TermInfoCharacter>>print: >> TermInfoCharacter>>set: >> TermInfoCharacter>>color: >> VTermOutputDriver>>color: >> VTermOutputDriver>>yellow: >> ImageWorker>>inform: >> >> >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org <mailto:pharo-dev-bounces@lists.pharo.org>] De la part de Valentin Ryckewaert >> EnvoyÃ© : lundi 11 juillet 2016 10:43 >> Ã : Pharo Development List >> Objet : Re: [Pharo-dev] VTermOutputDriver >> >> It looks like it's a problem of deleted methods executed (I deleted the method reset for example) >> I don't really see what i can do to solve this... >> >> 2016-07-11 10:39 GMT+02:00 Blondeau Vincent <vincent.blondeau(a)worldline.com <mailto:vincent.blondeau@worldline.com>>: >> Hi, >> >> You should check the stacktrace : https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/5662/console <https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/5662/console> >> >> Cheers, >> Vincent >> >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org <mailto:pharo-dev-bounces@lists.pharo.org>] De la part de Valentin Ryckewaert >> EnvoyÃ© : lundi 11 juillet 2016 10:35 >> Ã : Pharo Development List >> Objet : [Pharo-dev] VTermOutputDriver >> >> Hello everyone, >> >> I don't understand why my slice isn't working, could someone help me please? I just need a clue and I could fix the problem :) >> >> https://pharo.fogbugz.com/f/cases/18650 <https://pharo.fogbugz.com/f/cases/18650> >> >> Thanks, >> Valentin >> >> !!!************************************************************************************* >> "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.!!!" >> >> >> !!!************************************************************************************* >> "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.!!!" > >

July 11, 2016

Re: [Pharo-dev] VTermOutputDriver

by Valentin Ryckewaert

The problem is that my class have an outStream which is nil, it shouldn't be the case, i'm searching why right now, you think it's your modification which did that? 2016-07-11 11:15 GMT+02:00 Max Leske <maxleske(a)gmail.com>: > This seems to be a bug in the fix I recently made to ImageWorker > (althought the VTerm problem is another thingâ¦). Let me create a fix and > Iâll get back to you. > > Cheers, > Max > > > On 11 Jul 2016, at 10:48, Blondeau Vincent <vincent.blondeau(a)worldline.com> > wrote: > > That is not the pointâ¦ Look at the end: > > MessageNotUnderstood: receiver of "nextPutAll:" is nil > UndefinedObject(Object)>>doesNotUnderstand: #nextPutAll: > TermInfoCharacter>>print: > TermInfoCharacter>>set: > TermInfoCharacter>>color: > VTermOutputDriver>>color: > VTermOutputDriver>>yellow: > ImageWorker>>inform: > > > *De :* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org > <pharo-dev-bounces(a)lists.pharo.org>] *De la part de* Valentin Ryckewaert > *EnvoyÃ© :* lundi 11 juillet 2016 10:43 > *Ã :* Pharo Development List > *Objet :* Re: [Pharo-dev] VTermOutputDriver > > It looks like it's a problem of deleted methods executed (I deleted the > method reset for example) > I don't really see what i can do to solve this... > > 2016-07-11 10:39 GMT+02:00 Blondeau Vincent < > vincent.blondeau(a)worldline.com>: > Hi, > > You should check the stacktrace : > https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/5662/console > > Cheers, > Vincent > > *De :* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *De la part > de* Valentin Ryckewaert > *EnvoyÃ© :* lundi 11 juillet 2016 10:35 > *Ã :* Pharo Development List > *Objet :* [Pharo-dev] VTermOutputDriver > > Hello everyone, > > I don't understand why my slice isn't working, could someone help me > please? I just need a clue and I could fix the problem :) > > https://pharo.fogbugz.com/f/cases/18650 > > Thanks, > Valentin > > > !!!************************************************************************************* > "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.!!!" > > > > !!!************************************************************************************* > "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.!!!" > > >

July 11, 2016

Re: [Pharo-dev] VTermOutputDriver

by Max Leske

This seems to be a bug in the fix I recently made to ImageWorker (althought the VTerm problem is another thingâ¦). Let me create a fix and Iâll get back to you. Cheers, Max > On 11 Jul 2016, at 10:48, Blondeau Vincent <vincent.blondeau(a)worldline.com <mailto:vincent.blondeau@worldline.com>> wrote: > > That is not the pointâ¦ Look at the end: > > MessageNotUnderstood: receiver of "nextPutAll:" is nil > UndefinedObject(Object)>>doesNotUnderstand: #nextPutAll: > TermInfoCharacter>>print: > TermInfoCharacter>>set: > TermInfoCharacter>>color: > VTermOutputDriver>>color: > VTermOutputDriver>>yellow: > ImageWorker>>inform: > > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org <mailto:pharo-dev-bounces@lists.pharo.org>] De la part de Valentin Ryckewaert > EnvoyÃ© : lundi 11 juillet 2016 10:43 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] VTermOutputDriver > > It looks like it's a problem of deleted methods executed (I deleted the method reset for example) > I don't really see what i can do to solve this... > > 2016-07-11 10:39 GMT+02:00 Blondeau Vincent <vincent.blondeau(a)worldline.com <mailto:vincent.blondeau@worldline.com>>: > Hi, > > You should check the stacktrace : https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/5662/console <https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/5662/console> > > Cheers, > Vincent > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org <mailto:pharo-dev-bounces@lists.pharo.org>] De la part de Valentin Ryckewaert > EnvoyÃ© : lundi 11 juillet 2016 10:35 > Ã : Pharo Development List > Objet : [Pharo-dev] VTermOutputDriver > > Hello everyone, > > I don't understand why my slice isn't working, could someone help me please? I just need a clue and I could fix the problem :) > > https://pharo.fogbugz.com/f/cases/18650 <https://pharo.fogbugz.com/f/cases/18650> > > Thanks, > Valentin > > !!!************************************************************************************* > "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.!!!" > > > !!!************************************************************************************* > "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.!!!"

July 11, 2016

Re: [Pharo-dev] VTermOutputDriver

by Blondeau Vincent

That is not the pointâ¦ Look at the end: MessageNotUnderstood: receiver of "nextPutAll:" is nil UndefinedObject(Object)>>doesNotUnderstand: #nextPutAll: TermInfoCharacter>>print: TermInfoCharacter>>set: TermInfoCharacter>>color: VTermOutputDriver>>color: VTermOutputDriver>>yellow: ImageWorker>>inform: De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Valentin Ryckewaert EnvoyÃ© : lundi 11 juillet 2016 10:43 Ã : Pharo Development List Objet : Re: [Pharo-dev] VTermOutputDriver It looks like it's a problem of deleted methods executed (I deleted the method reset for example) I don't really see what i can do to solve this... 2016-07-11 10:39 GMT+02:00 Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>>: Hi, You should check the stacktrace : https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/5662/console Cheers, Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org<mailto:pharo-dev-bounces@lists.pharo.org>] De la part de Valentin Ryckewaert EnvoyÃ© : lundi 11 juillet 2016 10:35 Ã : Pharo Development List Objet : [Pharo-dev] VTermOutputDriver Hello everyone, I don't understand why my slice isn't working, could someone help me please? I just need a clue and I could fix the problem :) https://pharo.fogbugz.com/f/cases/18650 Thanks, Valentin !!!************************************************************************************* "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.!!!" !!!************************************************************************************* "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.!!!"

July 11, 2016

Re: [Pharo-dev] VTermOutputDriver

by Valentin Ryckewaert

It looks like it's a problem of deleted methods executed (I deleted the method reset for example) I don't really see what i can do to solve this... 2016-07-11 10:39 GMT+02:00 Blondeau Vincent <vincent.blondeau(a)worldline.com> : > Hi, > > > > You should check the stacktrace : > https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/5662/console > > > > Cheers, > > Vincent > > > > *De :* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *De la part > de* Valentin Ryckewaert > *EnvoyÃ© :* lundi 11 juillet 2016 10:35 > *Ã :* Pharo Development List > *Objet :* [Pharo-dev] VTermOutputDriver > > > > Hello everyone, > > > > I don't understand why my slice isn't working, could someone help me > please? I just need a clue and I could fix the problem :) > > > > https://pharo.fogbugz.com/f/cases/18650 > > > > Thanks, > > Valentin > > > !!!************************************************************************************* > "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.!!!" >

July 11, 2016

Re: [Pharo-dev] VTermOutputDriver

by Blondeau Vincent

Hi, You should check the stacktrace : https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/5662/console Cheers, Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Valentin Ryckewaert EnvoyÃ© : lundi 11 juillet 2016 10:35 Ã : Pharo Development List Objet : [Pharo-dev] VTermOutputDriver Hello everyone, I don't understand why my slice isn't working, could someone help me please? I just need a clue and I could fix the problem :) https://pharo.fogbugz.com/f/cases/18650 Thanks, Valentin !!!************************************************************************************* "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.!!!"

July 11, 2016

VTermOutputDriver

by Valentin Ryckewaert

Hello everyone, I don't understand when my slice isn't working, could someone help me please? I just need a clue and I could fix the problem :) https://pharo.fogbugz.com/f/cases/18650 Thanks, Valentin

July 11, 2016

Spec/FastTable context menus

by Nicolai Hess

We had some bugs like 18707 <https://pharo.fogbugz.com/f/cases/18707/Cannot-open-the-context-menu-in-Ver…> Cannot open the context menu in Versionner MenuMorph(Object)>>doesNotUnderstand: #addMenuGroup: I don't think the fix is right. We should not handle morphic objects in spec without an adapter. (and case 18584 <https://pharo.fogbugz.com/f/cases/18584/DNU-on-showing-menu-in-PointerExplo…> DNU on showing menu in PointerExplorer)

July 11, 2016

Re: [Pharo-dev] SessionManager and SystemSettings?

by Nicolai Hess

2016-07-10 23:49 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Settings should work now > > Yes! Thanks :-) > On 26 Jun 2016, at 04:56, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Thanks Yuriy! > > Last time, there was a problem on Jenkins. I do not have access to check > it or change it. > It is necessary that cleanUp process is called as a last command on > Jenkins. > > The other thing is to find out another solution. The current solution > expects that an instance variable is unset in a fresh (downloaded) image. > And this variable is set when the image is opened. > > Cheers, > Juraj > > On Jun 25, 2016, at 17:25, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > cc Juraj > > On 25 Jun 2016, at 22:28, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-06-23 15:32 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> > On 23 Jun 2016, at 15:29, Cyril Ferlicot Delbecque < >> cyril.ferlicot(a)gmail.com> wrote: >> > >> > >> > >> > On 23/06/2016 15:07, Christophe Demarey wrote: >> >> What happens if you execute >> >> 'SystemSettingsPersistence resumeSystemSettingsâ in a 60103 image? >> >> If nothing happens, it could be that 'SystemSettingsPersistence >> >> instVarNamed: âalreadyResumedââ is true >> >> >> >> I checked the startupList and PharoCommandLineHandler>>#runPreferences >> >> but nothing changed there. >> >> >> >> >> > >> > >> > I think I read something about a script esteban added to clear the >> > ever-growing stack. Couldn't it be that? Maybe it open the image and the >> >> > system setting think he already loaded the settings. >> >> no it shouldnâtâ¦ and *my* preferences are correctly loaded :) >> > > Can we please fix this. > I work a lot with fresh images, and now every time a start a new image and > trying to access a repository I have to remmember > to set the network proxy settings. > > >> >> > >> >> >> > >> > -- >> > Cyril Ferlicot >> > >> > http://www.synectique.eu >> > >> > 165 Avenue Bretagne >> > Lille 59000 France >> > >> > > > >

July 11, 2016

Re: [Pharo-dev] changing compiled byte arrays

by Tudor Girba

Thanks, indeed! Doru > On Jul 10, 2016, at 7:28 PM, stepharo <stepharo(a)free.fr> wrote: > > thanks for all the energy you put in getting non mutable objects. I will bring a nicer system. > > Stef > > Le 10/7/16 Ã 12:06, ClÃ©ment Bera a Ã©crit : >> Allright. But the problem happens for any literal you mutate, not only byte arrays. >> >> For example this one: >> >> foo >> #(true nil 10) at: 2 put: 50. >> ^ #(true nil 10) >> >> Answers... #(true 50 10) >> >> The most common problems are with Array, not ByteArray. >> >> Even worse, it can happen with LargeIntegers, Floats, ScaledDecimal, etc. >> >> Hopefully read-only objects will solve most of the problems. >> >> >> >> On Sun, Jul 10, 2016 at 10:51 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> Thanks for the explanation! >> >> I've this byte array syntax for the first time and I don't think that I will be making heavy use of it, so it shouldn't be a too big problem â since now I understand the behavior, so I can keep it in mind. >> >> Thanks, >> Peter >> >> On Sun, Jul 10, 2016 at 7:43 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> This is the normal behavior. You are mutating the method's literal, which becomes different. The instance is per method, so even if you do: >> >> foo >> #[1 2 3] at: 2 put: 50. >> ^ #[1 2 3] >> >> You get #[1 50 3], which is easy to understand in this example, but can be very tricky to understand in some cases. >> >> I've introduced recently "read-only" objects (Object>>#isReadOnlyObject and co). I am waiting for the VM repo merge which should happen in the next few weeks to have this feature in the default Pharo VM, then I will be able to compile method literals "read-only" by default. With this feature, the #at:put: store will fail telling you that you cannot store into a read-only object, which will solve the common problem, when one does not mutate a literal on purpose. >> >> Now as in Pharo everything is reflective, it will always be possible to mark back the literal as "writable", mutate it, and still have this behavior. >> >> Best, >> Clement >> >> >> On Sat, Jul 9, 2016 at 10:22 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> Is this normal behavior? >> >> cls := Object subclass: #Something. >> >> cls compile: 'array >> ^ #[1 2 3 4]'. >> >> cls new array. "#[1 2 3 4]" >> >> cls new array at: 1 put: 55. >> >> cls new array. "#[55 2 3 4]" >> >> (cls>>#array) sourceCode "'array >> ^ #[1 2 3 4]'" >> >> >> So I can permanently change the compiled byte array in the method, which is weird. >> >> Shouldn't the behavior be either >> >> a) don't change the original byte array >> >> or >> >> b) change the source code >> >> Thanks, >> Peter >> >> >> > -- www.tudorgirba.com www.feenk.com "We cannot reach the flow of things unless we let go."

July 11, 2016