- Pharo-users - lists.pharo.org

Re: Sharing classes between packages

by David＠totallyobjects.com

March 1, 2021

Sharing classes between packages

by David Pennington

I have a small Key/Value database that I have written for my Seaside apps. I have one Package - Family-Accounts which defines the classes for this database. I am now writing a new Seaside app (IPMSClacton) that will also need to use the database. How do I share the code between the two packages? David Totally Objects

March 1, 2021

Re: Strings in Playground are read only in Pharo 9

by Richard O'Keefe

For what it's worth, the ANSI Smalltalk standard says "The protocols specified for literals do not include any messages that modify the state of the literal objects. The effect of sending a message to an object that is the value of a literal that modifies the state of the literal is undefined." This also includes trying to modify an array literal, and fiddling with the bits of a large integer. That is, according to the ANSI standard, 'abc' is a string but not necessarily a String. I hope that is clear (:-). On Sun, 28 Feb 2021 at 22:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Markus, > > 'hello' is a literal string constant, part of the set of constants of a > method (or a doit which like a temporary method disconnected from a class). > > Constants like these are managed by the compiler and can be shared between > different expressions to avoid duplication. > > Changing such a constant is dangerous because it means you are changing > static/compiled code. Consider a method like > > name > ^ 'Markus' > > I could call this method and change the returned string destructively in > place. Next time someone calls it, s/he would get the modified string. Even > worse, s/he would not understand since the source code did not change. > > In the past it was not possible to mark such strings as being constant, > now we can. Which is a big win. > > You can use #copy to get a string that you can modify. > > 'hello' copy at: 2 put: $a; yourself > > HTH, > > Sven > > > On 28 Feb 2021, at 00:50, Markus Wedel <mail(a)markus-wedel.de> wrote: > > > > Hi all, > > > > strings in Playground are read only in Pharo 9.0 Build 1153 so that > > > > 'hello' at: 2 put: $a; yourself > > ctrl+p > > > > This throws an error: > > âModification forbidden: âhelloâ is read-only, hence its field cannot be > modified with $a > > > > which is actually a very nice error message but is this supposed to > happen? > > The example does work in Pharo 8 without problems. > > > > > > Greetings > > Markus >

March 1, 2021

Re: Error in Pharo 9 under Windows 10

by lb

Hi Nacho, Pls update VM å¨ 2021-03-01 04:56:04ï¼"Rafael Ignacio MatÃas Sniechowski" <0800nacho(a)gmail.com> åéï¼ Hi, Every time I try to start a Pharo 9 image I get an error. This happens with both 32 and 64 bit versions, under Windows 10. I've tried uninstalling and reinstalling Pharo Launcher without avail. This has been happening for the last 10 days. I don't know if this is the proper place to post this...if not please let me know. Attached it's an image with the error I get. thanks in advance Nacho Ignacio Sniechowski

March 1, 2021

Error in Pharo 9 under Windows 10

by Rafael Ignacio MatÃas Sniechowski

Hi, Every time I try to start a Pharo 9 image I get an error. This happens with both 32 and 64 bit versions, under Windows 10. I've tried uninstalling and reinstalling Pharo Launcher without avail. This has been happening for the last 10 days. I don't know if this is the proper place to post this...if not please let me know. Attached it's an image with the error I get. thanks in advance Nacho *Ignacio Sniechowski*

Feb. 28, 2021

Re: Strings in Playground are read only in Pharo 9

by Markus Wedel

Hello Sven, thank you very much for this thorough explanation! I also think a string literal should be a constant. But since I am new to Smalltalk I am reading a lot of documentation, and in the older documentation modification of a string was shown as an example. In fact this modification is still possible in Pharo 8. But I am all for progress and evolution of Smalltalk for the better and this is how it was meant to be by itâs inventors. Again thank you very much for your time Markus Von meinem iPad gesendet > Am 28.02.2021 um 10:57 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > ï»¿Markus, > > 'hello' is a literal string constant, part of the set of constants of a method (or a doit which like a temporary method disconnected from a class). > > Constants like these are managed by the compiler and can be shared between different expressions to avoid duplication. > > Changing such a constant is dangerous because it means you are changing static/compiled code. Consider a method like > > name > ^ 'Markus' > > I could call this method and change the returned string destructively in place. Next time someone calls it, s/he would get the modified string. Even worse, s/he would not understand since the source code did not change. > > In the past it was not possible to mark such strings as being constant, now we can. Which is a big win. > > You can use #copy to get a string that you can modify. > > 'hello' copy at: 2 put: $a; yourself > > HTH, > > Sven > >> On 28 Feb 2021, at 00:50, Markus Wedel <mail(a)markus-wedel.de> wrote: >> >> Hi all, >> >> strings in Playground are read only in Pharo 9.0 Build 1153 so that >> >> 'hello' at: 2 put: $a; yourself >> ctrl+p >> >> This throws an error: >> âModification forbidden: âhelloâ is read-only, hence its field cannot be modified with $a >> >> which is actually a very nice error message but is this supposed to happen? >> The example does work in Pharo 8 without problems. >> >> >> Greetings >> Markus

Feb. 28, 2021

Re: Strings in Playground are read only in Pharo 9

by Sven Van Caekenberghe

Markus, 'hello' is a literal string constant, part of the set of constants of a method (or a doit which like a temporary method disconnected from a class). Constants like these are managed by the compiler and can be shared between different expressions to avoid duplication. Changing such a constant is dangerous because it means you are changing static/compiled code. Consider a method like name ^ 'Markus' I could call this method and change the returned string destructively in place. Next time someone calls it, s/he would get the modified string. Even worse, s/he would not understand since the source code did not change. In the past it was not possible to mark such strings as being constant, now we can. Which is a big win. You can use #copy to get a string that you can modify. 'hello' copy at: 2 put: $a; yourself HTH, Sven > On 28 Feb 2021, at 00:50, Markus Wedel <mail(a)markus-wedel.de> wrote: > > Hi all, > > strings in Playground are read only in Pharo 9.0 Build 1153 so that > > 'hello' at: 2 put: $a; yourself > ctrl+p > > This throws an error: > âModification forbidden: âhelloâ is read-only, hence its field cannot be modified with $a > > which is actually a very nice error message but is this supposed to happen? > The example does work in Pharo 8 without problems. > > > Greetings > Markus

Feb. 28, 2021

Strings in Playground are read only in Pharo 9

by Markus Wedel

Hi all, strings in Playground are read only in Pharo 9.0 Build 1153 so that 'hello' at: 2 put: $a; yourself ctrl+p This throws an error: âModification forbidden: âhelloâ is read-only, hence its field cannot be modified with $a which is actually a very nice error message but is this supposed to happen? The example does work in Pharo 8 without problems. Greetings Markus

Feb. 27, 2021

[ANN] Next Pharo Sprint: Feb 26

by Marcus Denker

We will organize a Pharo sprint Feb 26 (this Friday) Goals of this sprint: - Fix issues from tracker https://github.com/pharo-project/pharo/issues This is a Remote Sprint, it happens on Discord. http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9

Feb. 24, 2021

Re: [Pharo-dev] StackVM for M1 ready

by StÃ©phane Ducasse

Doru we will try to run Bloc on it too. Martin run Bloc on P9 on a VM that Pablo should release officially, but Martin went on vacation. And after we want to see with the JIT ;) S > On 17 Feb 2021, at 22:55, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Awesome news! > > Thank you for all this work! > > Doru > >> On Feb 16, 2021, at 8:38 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> Hello happy Pharoers >> >> Today we could access our building where the M1 machine is and Pablo packaged it >> so that you can test the first version. >> >> Pablo wrote a little blog post for you. >> >> https://thepharo.dev/2021/02/16/first-apple-m1-pharo-version/ >> >> Let us since we do not have the M1 at hand and waiting to be able to make it accessible from >> our build farmâ¦ but we are not responsible for it and we were waitingâ¦. >> But the crew was fixing other VM glitches. So we will be ready soon to focus on the Jit version. >> >> >> S >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Aurore Dalle >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> > > -- > feenk.com > > "If you interrupt the barber while he is cutting your hair, > you will end up with a messy haircut." -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Feb. 18, 2021