- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Better management of encoding of environment variables

by David T. Lewis

On Fri, Jan 18, 2019 at 08:58:07AM -0500, David T. Lewis wrote: > On Fri, Jan 18, 2019 at 01:40:26PM +0100, Sven Van Caekenberghe wrote: > > > > > On 18 Jan 2019, at 01:54, David T. Lewis via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > > > > On Thu, Jan 17, 2019 at 04:57:18PM +0100, Sven Van Caekenberghe wrote: > > >> > > >> Right, bytes are always uninterpreted, else they would be something else. > > >> We got ByteArray>>#decodedWith: and ByteArray>>#utf8Decoded and our ByteArray > > >> inspector decodes automatically if it can. > > > > > > Hi Sven, > > > > > > I am the author of the getenv primitives, and I am also sadly uninformed > > > about matters of character sets and strings in a multilingual environment. > > > > > > The primitives answer environment variable variable values as ByteString > > > rather than ByteArray. This made sense to me at the time that I wrote it, > > > because ByteString is easy to display in an inspector, and because it is > > > easily converted to ByteArray. > > > > > > For an American English speaker this seems like a good choice, but I > > > wonder now if it is a bad decision. After all, it is also trivially easy > > > to convert a ByteArray to ByteString for display in the image. > > > > > > Would it be helpful to have getenv primitives that answer ByteArray > > > instead, and to let all conversion (including in OSProcess) be done in > > > the image? > > > > > > Thanks, > > > Dave > > > > Normally, the correct way to represent uninterpreted bytes is with a > > ByteArray. Decoding these bytes as characters is the specific task of > > a character encoder/decoder, with a deliberate choice as to which to use. > > > > Since the getenv() system call uses simple C strings, it is understandable > > that this was carried over. It is probably not worth or too risky to > > change that - as long as the receiver understands that it is a raw OS > > string that needs more work. > > > > Like with file path encoding/decoding, environment variable encoding/decoding > > is plain messy and complex. IMHO it is better to manage that at the > > image level where we are more agile and can better handle that complexity. > > > > Thanks Sven, that makes perfect sense to me. > I added some new primitives to OSProcessPlugin that answer ByteArray instead of ByteString. For Unix (Linux, OS X): <primitive: 'primitiveGetCurrentWorkingDirectoryAsBytes' module: 'UnixOSProcessPlugin'> <primitive: 'primitiveArgumentAtAsBytes' module: 'UnixOSProcessPlugin'> <primitive: 'primitiveEnvironmentAtAsBytes' module: 'UnixOSProcessPlugin'> <primitive: 'primitiveEnvironmentAtSymbolAsBytes' module: 'UnixOSProcessPlugin'> <primitive: 'primitiveRealpathAsBytes' module: 'UnixOSProcessPlugin'> For Windows: <primitive: 'primitiveGetCurrentWorkingDirectoryAsBytes' module: 'Win32OSProcessPlugin'> <primitive: 'primitiveGetEnvironmentStringsAsBytes' module: 'Win32OSProcessPlugin'> These should be in the latest VM builds now. If you are using OSProcess, update it to the latest version to get accessor methods for the new primitives. For example, OSProcess accessor primGetCurrentWorkingDirectory calls the original primitive that answers a ByteString, and to get raw bytes you can use OSProcess accessor primGetCurrentWorkingDirectoryAsBytes instead. Dave

Jan. 27, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by ducasse

Hi everybody > On 24 Jan 2019, at 20:36, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > it's a nice release yes - and the best we ever provided indeed. I'm really happy too that P7 image is an > official release now. > > > But still: > ========== > > In a post [1] in November 2017 I brought up the topic again to "increase the quality level in Pharo 7 and onwards". > > With 762 commits [2] for Pharo 7 I devoted a lot of time in fixing often simple and trivial things just to clean up > comments, code, typos, packages, manifests, tests and so on. Thanks for it. > > Many others did the same and supported these cleaning efforts. This helped adding a few more release tests to keep the > quality bar on the level reached. Special thanks to Marcus, Esteban, and many others who helped reviewing, fighting a > shaky CI server, integrating quickly and so on â¦ Yes. I think that with Iceberg and git we can now be a lot faster to integrate simple fixes. > Still THIS IS NOT FINISHED ... and it would be really help if more people would participate in the cleaning or fixing bugs. > Also many external packages now need some love to work with Pharo 7. Definitively. What is important is that when we have to deal with little issues this is difficult to work on larger ones. Iâm resurrecting the code of the classParser and UndefinedClasses right now (checking/adding tests). > We have a large community with many, many users - but still only a few contribute to the core system. > > I wonder why and would like to know: > - Is it due to the switch to git ? > - Is is due to the new contribution process? > - Is it for other reasons? > > Remember: Pharo is yours and even small steps could make a difference. So please join! Thanks this is a good message. We will produce a video during the next techTalk showing how easy it is to contribute. > Thanks > T. > > > [1] http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-an… > [2] https://github.com/pharo-project/pharo/graphs/contributors > >

Jan. 26, 2019

Re: [Pharo-dev] [Off Topic] Michel Bauwens on the history and immediate future of work

by ducasse

Thanks we will watch it > On 25 Jan 2019, at 17:41, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: > > Hi All, > > I find this talk profound and key to making functional open source communities as we try and survive. > > Iâve skipped an introduction in Portuguese and some slide control issues. > https://youtu.be/vDjazcMm-eE?t=4m40s <https://youtu.be/vDjazcMm-eE?t=4m40s> > _,,,^..^,,,_ (phone)

Jan. 26, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by ducasse

Hello > > Torsten Bergmann wrote >> We have a large community with many, many users - but still only a few >> contribute to the core system. >> >> I wonder why and would like to know: >> - Is it due to the switch to git ? >> - Is is due to the new contribution process? >> - Is it for other reasons? > > For me; a combination of 1 and 2. > I've done work in Pharo 6.1 during the Pharo7 process, but had no idea how > to easily forward-port any base fixes to Pharo 7. The times I tried (after a > good old-fashioned file-out), I failed to get Iceberg check out Pharo7 on > Windows. > IIRC, I believe I resorted to posting an .st in the issues (which then timed > out after a year of being stuck in for review status with no automatical > validation) > As such, I'm absent from the contributor list for the first time since... > Pharo 1.1? ;) > > I hope switching to Pharo8 branch and commiting fixes while working in > Pharo7 will be easier? I can tell you. It is a **lot** easier can you tell us if the following is understandable for you https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> > > Cheers, > Henry > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Jan. 26, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by ducasse

Now github. Stef > On 24 Jan 2019, at 20:44, Eric Gade <eric.gade(a)gmail.com> wrote: > > Which is now the canonical place to seek out these issues/bugs: manuscript or GitHub? > > On Thu, Jan 24, 2019, 14:37 Torsten Bergmann <astares(a)gmx.de <mailto:astares@gmx.de> wrote: > Hi, > > it's a nice release yes - and the best we ever provided indeed. I'm really happy too that P7 image is an > official release now. > > > But still: > ========== > > In a post [1] in November 2017 I brought up the topic again to "increase the quality level in Pharo 7 and onwards". > > With 762 commits [2] for Pharo 7 I devoted a lot of time in fixing often simple and trivial things just to clean up > comments, code, typos, packages, manifests, tests and so on. > > Many others did the same and supported these cleaning efforts. This helped adding a few more release tests to keep the > quality bar on the level reached. Special thanks to Marcus, Esteban, and many others who helped reviewing, fighting a > shaky CI server, integrating quickly and so on ... > > Still THIS IS NOT FINISHED ... and it would be really help if more people would participate in the cleaning or fixing bugs. > Also many external packages now need some love to work with Pharo 7. > > We have a large community with many, many users - but still only a few contribute to the core system. > > I wonder why and would like to know: > - Is it due to the switch to git ? > - Is is due to the new contribution process? > - Is it for other reasons? > > Remember: Pharo is yours and even small steps could make a difference. So please join! > > Thanks > T. > > > [1] http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-an… <http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-an…> > [2] https://github.com/pharo-project/pharo/graphs/contributors <https://github.com/pharo-project/pharo/graphs/contributors> > >

Jan. 26, 2019

Re: [Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

by Dale Henrichs

Thanks, Nicolas (and Sven), VM search path is what I am looking for (UFFI external modules) and I am curious whether or not this path `pharo-vm/lib/pharo/5.0-201806281256` is constant or variable for the various Pharo versions or does it vary based on the vm version/build number ... pharo6.0 and pharo.1 appear to have the same path ... haven't looked at Pharo7.0 ... and hopefully the path is the same for mac and unix or does it vary ... I don't have a mac to readily test on:) The bash script that copies my unix/mac .so/.dylib files will be run immediately after the image and vm have been downloaded so I won't be running the image itself (unless I have to). Currently, the download, installation and build of the pharo client for GemStone is built by a bash script... I'm going to assume for now that the gci libraries will be shoveled into the pharo-vm/lib/5.0-* directory until someone gives me a more definitive answer... Dale On 1/25/19 12:27 PM, Nicolas Cellier wrote: > Oh, maybe you're after PharoLauncher conventions? > I was talking of underlying VM search path. > I remember that the library loading happens in ioLoadModule() both for > FFI and external plugins. > https://github.com/OpenSmalltalk/opensmalltalk-vm/search?q=ioLoadModule&uns… > > LeÂ ven. 25 janv. 2019 Ã Â 18:45, Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>> a Ã©critÂ : > > Maybe FileLocator can help ? > > on macOS > > FileLocator vmDirectory pathString. > "'/Users/sven/Develop/Pharo/Pharo-Daily/2019-01-24/pharo-vm'" > > FileLocator vmBinary pathString. > "'/Users/sven/Develop/Pharo/Pharo-Daily/2019-01-24/pharo-vm/Pharo.app/Contents/MacOS/Pharo'" > > on Linux > > $ ../bin/pharo Pharo.image eval 'FileLocator vmDirectory pathString' > '/home/t3/pharo/bin/pharo-vm' > > $ ../bin/pharo Pharo.image eval 'FileLocator vmBinary pathString' > '/home/t3/pharo/bin/pharo-vm/pharo' > > > On 25 Jan 2019, at 18:25, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>> wrote: > > > > Thanks Nicolas, > > > > Is it as simple as pharo/*, or could there be multiple > directories created and I need to pick the right one? > > > > Dale > > > > On 1/25/19 12:48 AM, Nicolas Cellier wrote: > >> I'm afraid it also depends on the overly complex rules burried > deep inside the VM... > >> It would be a good thing to try and document it. > >> And if we can't reasonably document it, then we might want to > open an issue on opensmalltalk. > >> > >> Le ven. 25 janv. 2019 Ã 01:51, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>> a Ã©crit : > >> I am in the process of porting the GemStone-GCI[1] project to > Pharo6.1 > >> (32 bit) and Pharo7.0 (64 bit) and I'm curious what the naming > >> convention for the library directories are. > >> > >> For Pharo5.0 and earlier, I copied my 32 bit gemstone gci > library files > >> (.so on linux) into the pharo-vm directory. > >> > >> For Pharo6.1 I just figured out that I need to copy the gci > library > >> files into the pharo-vm/lib/pharo/5.0-201806281256 directory > ... at list > >> the libraries are found when I do so? > >> > >> I would like to be able to write a bash script that copies the gci > >> library files into the proper directory, but the directory for the > >> Pharo6.1 vm looks like some kind of magic number and I assume that > >> different builds of the 6.1 vm could have different names and > possibly > >> even multiple directories under pharo-vm/lib/pharo/? > >> > >> I haven't looked at Pharo7.0 yet to see what it's pharo-vm > directory > >> structure looks like... > >> > >> A pointer to where the naming conventions for these directories is > >> described for Pharo6.x, Pharo7.x and Pharo8.x would be greatly > >> appreciated ... would also be nice if the error message for the > "module > >> not found" error could be a bit more descriptive as well ... > >> > >> Thanks, > >> > >> Dale > >> > >> [1] https://github.com/GsDevKit/GemStone-GCI > >> > >> > >

Jan. 25, 2019

Re: [Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

by Nicolas Cellier

Oh, maybe you're after PharoLauncher conventions? I was talking of underlying VM search path. I remember that the library loading happens in ioLoadModule() both for FFI and external plugins. https://github.com/OpenSmalltalk/opensmalltalk-vm/search?q=ioLoadModule&uns… Le ven. 25 janv. 2019 Ã 18:45, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > Maybe FileLocator can help ? > > on macOS > > FileLocator vmDirectory pathString. > "'/Users/sven/Develop/Pharo/Pharo-Daily/2019-01-24/pharo-vm'" > > FileLocator vmBinary pathString. > > "'/Users/sven/Develop/Pharo/Pharo-Daily/2019-01-24/pharo-vm/Pharo.app/Contents/MacOS/Pharo'" > > on Linux > > $ ../bin/pharo Pharo.image eval 'FileLocator vmDirectory pathString' > '/home/t3/pharo/bin/pharo-vm' > > $ ../bin/pharo Pharo.image eval 'FileLocator vmBinary pathString' > '/home/t3/pharo/bin/pharo-vm/pharo' > > > On 25 Jan 2019, at 18:25, Dale Henrichs < > dale.henrichs(a)gemtalksystems.com> wrote: > > > > Thanks Nicolas, > > > > Is it as simple as pharo/*, or could there be multiple directories > created and I need to pick the right one? > > > > Dale > > > > On 1/25/19 12:48 AM, Nicolas Cellier wrote: > >> I'm afraid it also depends on the overly complex rules burried deep > inside the VM... > >> It would be a good thing to try and document it. > >> And if we can't reasonably document it, then we might want to open an > issue on opensmalltalk. > >> > >> Le ven. 25 janv. 2019 Ã 01:51, Dale Henrichs < > dale.henrichs(a)gemtalksystems.com> a Ã©crit : > >> I am in the process of porting the GemStone-GCI[1] project to Pharo6.1 > >> (32 bit) and Pharo7.0 (64 bit) and I'm curious what the naming > >> convention for the library directories are. > >> > >> For Pharo5.0 and earlier, I copied my 32 bit gemstone gci library files > >> (.so on linux) into the pharo-vm directory. > >> > >> For Pharo6.1 I just figured out that I need to copy the gci library > >> files into the pharo-vm/lib/pharo/5.0-201806281256 directory ... at > list > >> the libraries are found when I do so? > >> > >> I would like to be able to write a bash script that copies the gci > >> library files into the proper directory, but the directory for the > >> Pharo6.1 vm looks like some kind of magic number and I assume that > >> different builds of the 6.1 vm could have different names and possibly > >> even multiple directories under pharo-vm/lib/pharo/? > >> > >> I haven't looked at Pharo7.0 yet to see what it's pharo-vm directory > >> structure looks like... > >> > >> A pointer to where the naming conventions for these directories is > >> described for Pharo6.x, Pharo7.x and Pharo8.x would be greatly > >> appreciated ... would also be nice if the error message for the "module > >> not found" error could be a bit more descriptive as well ... > >> > >> Thanks, > >> > >> Dale > >> > >> [1] https://github.com/GsDevKit/GemStone-GCI > >> > >> > > >

Jan. 25, 2019

Re: [Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

by Sven Van Caekenberghe

Maybe FileLocator can help ? on macOS FileLocator vmDirectory pathString. "'/Users/sven/Develop/Pharo/Pharo-Daily/2019-01-24/pharo-vm'" FileLocator vmBinary pathString. "'/Users/sven/Develop/Pharo/Pharo-Daily/2019-01-24/pharo-vm/Pharo.app/Contents/MacOS/Pharo'" on Linux $ ../bin/pharo Pharo.image eval 'FileLocator vmDirectory pathString' '/home/t3/pharo/bin/pharo-vm' $ ../bin/pharo Pharo.image eval 'FileLocator vmBinary pathString' '/home/t3/pharo/bin/pharo-vm/pharo' > On 25 Jan 2019, at 18:25, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > Thanks Nicolas, > > Is it as simple as pharo/*, or could there be multiple directories created and I need to pick the right one? > > Dale > > On 1/25/19 12:48 AM, Nicolas Cellier wrote: >> I'm afraid it also depends on the overly complex rules burried deep inside the VM... >> It would be a good thing to try and document it. >> And if we can't reasonably document it, then we might want to open an issue on opensmalltalk. >> >> Le ven. 25 janv. 2019 Ã 01:51, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> a Ã©crit : >> I am in the process of porting the GemStone-GCI[1] project to Pharo6.1 >> (32 bit) and Pharo7.0 (64 bit) and I'm curious what the naming >> convention for the library directories are. >> >> For Pharo5.0 and earlier, I copied my 32 bit gemstone gci library files >> (.so on linux) into the pharo-vm directory. >> >> For Pharo6.1 I just figured out that I need to copy the gci library >> files into the pharo-vm/lib/pharo/5.0-201806281256 directory ... at list >> the libraries are found when I do so? >> >> I would like to be able to write a bash script that copies the gci >> library files into the proper directory, but the directory for the >> Pharo6.1 vm looks like some kind of magic number and I assume that >> different builds of the 6.1 vm could have different names and possibly >> even multiple directories under pharo-vm/lib/pharo/? >> >> I haven't looked at Pharo7.0 yet to see what it's pharo-vm directory >> structure looks like... >> >> A pointer to where the naming conventions for these directories is >> described for Pharo6.x, Pharo7.x and Pharo8.x would be greatly >> appreciated ... would also be nice if the error message for the "module >> not found" error could be a bit more descriptive as well ... >> >> Thanks, >> >> Dale >> >> [1] https://github.com/GsDevKit/GemStone-GCI >> >>

Jan. 25, 2019

Re: [Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

by Dale Henrichs

Thanks Nicolas, Is it as simple as pharo/*, or could there be multiple directories created and I need to pick the right one? Dale On 1/25/19 12:48 AM, Nicolas Cellier wrote: > I'm afraid it also depends on the overly complex rules burried deep > inside the VM... > It would be a good thing to try and document it. > And if we can't reasonably document it, then we might want to open an > issue on opensmalltalk. > > LeÂ ven. 25 janv. 2019 Ã Â 01:51, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>> a Ã©critÂ : > > I am in the process of porting the GemStone-GCI[1] project to > Pharo6.1 > (32 bit) and Pharo7.0 (64 bit) and I'm curious what the naming > convention for the library directories are. > > For Pharo5.0 and earlier, I copied my 32 bit gemstone gci library > files > (.so on linux) into the pharo-vm directory. > > For Pharo6.1 I just figured out that I need to copy the gci library > files into the pharo-vm/lib/pharo/5.0-201806281256 directory ... > at list > the libraries are found when I do so? > > I would like to be able to write a bash script that copies the gci > library files into the proper directory, but the directory for the > Pharo6.1 vm looks like some kind of magic number and I assume that > different builds of the 6.1 vm could have different names and > possibly > even multiple directories under pharo-vm/lib/pharo/? > > I haven't looked at Pharo7.0 yet to see what it's pharo-vm directory > structure looks like... > > A pointer to where the naming conventions for these directories is > described for Pharo6.x, Pharo7.x and Pharo8.x would be greatly > appreciated ... would also be nice if the error message for the > "module > not found" error could be a bit more descriptive as well ... > > Thanks, > > Dale > > [1] https://github.com/GsDevKit/GemStone-GCI > >

Jan. 25, 2019

[Off Topic] Michel Bauwens on the history and immediate future of work

by Eliot Miranda

Hi All, I find this talk profound and key to making functional open source communities as we try and survive. Iâve skipped an introduction in Portuguese and some slide control issues. https://youtu.be/vDjazcMm-eE?t=4m40s _,,,^..^,,,_ (phone)

Jan. 25, 2019