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

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

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

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_q=ioLoadModule Le ven. 25 janv.

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

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

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

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

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

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)

Re: [Pharo-dev] [Pharo-users] macOS VM builds with AddressSanitizer/LeakSanitizer

Hi Ben, Thanks for the pointer, I subscribed to those two mailing lists as well. Cheers, Manuel > On 25 Jan 2019, at 14:25, Ben Coman wrote: > > Hi Manuel, > > This level question would be better handled on pharo-dev and vm-dev mail > lists (forwarded a copy). >

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

Congrats on the release, a major leap forward! 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

[Pharo-dev] [Pharo 8.0] Build #25: 2302-Context comment typos

There is a new Pharo build available! The status of the build #25 was: FAILURE. The Pull Request #2286 was integrated: "2302-Context comment typos" Pull request url: https://github.com/pharo-project/pharo/pull/2286 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url:

[Pharo-dev] [Pharo 8.0] Build #24: 2302-Context comment typos

There is a new Pharo build available! The status of the build #24 was: FAILURE. The Pull Request #2286 was integrated: "2302-Context comment typos" Pull request url: https://github.com/pharo-project/pharo/pull/2286 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url:

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

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 <

[Pharo-dev] [Pharo 8.0] Build #23: 2302-Context comment typos

There is a new Pharo build available! The status of the build #23 was: FAILURE. The Pull Request #2286 was integrated: "2302-Context comment typos" Pull request url: https://github.com/pharo-project/pharo/pull/2286 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url: