- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] FFI without the Pharo sources

by Marcus Denker

> On 24 Jan 2018, at 08:58, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 24 Jan 2018, at 01:54, <Vincent.Blondeau(a)lamresearch.com> <Vincent.Blondeau(a)lamresearch.com> wrote: >> >> Hi, >> >> I am working to be able to create some standalone apps in Pharo. And for this, I would like to remove of the .sources and .changes. But, by removing them, the args names are reset to arg1, arg2, arg3, ... and the FFI cannot be used anymore. >> >> Does someone (Esteban?) have a solution that I could implement to fix this issue? >> > > Hello, > > You can embed the sources of just those methods: > -> iterate over all methods, select the FFI methods > -> call #embeddSourceInTrailer on these methods. > We should add later something to the compiler for this, too. Imagine you have your system without source, decompiling happily. Then you want to edit a method: -> if it was decompiled, just compile and drop source -> if the source comes from the trailer, it should again compile a method with embedded source. I make a note for my TODO. With Pavel we managed to speed up source reading for methods that have embeddSourceInTrailer quite a lot (with ideas for even more), I will start to merge these patches, too. Marcus

Jan. 24, 2018

Re: [Pharo-dev] [Launcher][Win]Cannot download the VM from Pharo

by Marcus Denker

Hi, My watchdog detected problems connecting to files.pharo.org <http://files.pharo.org/> this night (local time). It seems to not happen anymore. It might have been related (that is, there might have been problems on the OVH side this night). Marcus > On 24 Jan 2018, at 00:09, <Vincent.Blondeau(a)lamresearch.com> <Vincent.Blondeau(a)lamresearch.com> wrote: > > Hi, > > With the Pharo launcher, the VM are automatically downloaded from the files.pharo.org server. > However, it seems that the download of some VMs doesn't work at least under Windows 10. > For the P7 image, the download stops at 38% (~2.5Mo) with the error "ConnectionClosed: Cannot Read Data", and, I obtain the same error with this cmd: > > ZnEasy get: 'http://files.pharo.org/get-files/70/pharo-win-stable.zip'. > > However, I can fully download the image through the Internet Browser. The download with Pharo is working: ZnEasy get: 'https://files.pharo.org/'. give me a 200 OK response. > > Thanks in advance for your help, > > Cheers, > Vincent > > > <winmail.dat>

Jan. 24, 2018

Re: [Pharo-dev] FFI without the Pharo sources

by Marcus Denker

> On 24 Jan 2018, at 01:54, <Vincent.Blondeau(a)lamresearch.com> <Vincent.Blondeau(a)lamresearch.com> wrote: > > Hi, > > I am working to be able to create some standalone apps in Pharo. And for this, I would like to remove of the .sources and .changes. But, by removing them, the args names are reset to arg1, arg2, arg3, ... and the FFI cannot be used anymore. > > Does someone (Esteban?) have a solution that I could implement to fix this issue? > Hello, You can embed the sources of just those methods: -> iterate over all methods, select the FFI methods -> call #embeddSourceInTrailer on these methods. Marcus

Jan. 24, 2018

Re: [Pharo-dev] FFI without the Pharo sources

by Ben Coman

On 24 January 2018 at 08:54, <Vincent.Blondeau(a)lamresearch.com> wrote: > Hi, > > I am working to be able to create some standalone apps in Pharo. And for this, I would like to remove of the .sources and .changes. But, by removing them, the args names are reset to arg1, arg2, arg3, ... and the FFI cannot be used anymore. > > Does someone (Esteban?) have a solution that I could implement to fix this issue? > > Thanks! > > Vincent Is removing those files to reduce deployment size? Or to keep code private? Just guessing, but you may be able to file-out the FFI definitions, remove the .changes and .sources files, then file-in FFI definitons. You'll end up with a .changes file, but much smaller. cheers -ben

Jan. 24, 2018

FFI without the Pharo sources

by Vincent.Blondeau＠lamresearch.com

Hi, I am working to be able to create some standalone apps in Pharo. And for this, I would like to remove of the .sources and .changes. But, by removing them, the args names are reset to arg1, arg2, arg3, ... and the FFI cannot be used anymore. Does someone (Esteban?) have a solution that I could implement to fix this issue? Thanks! Vincent

Jan. 24, 2018

[Launcher][Win]Cannot download the VM from Pharo

by Vincent.Blondeau＠lamresearch.com

Hi, With the Pharo launcher, the VM are automatically downloaded from the files.pharo.org server. However, it seems that the download of some VMs doesn't work at least under Windows 10. For the P7 image, the download stops at 38% (~2.5Mo) with the error "ConnectionClosed: Cannot Read Data", and, I obtain the same error with this cmd: ZnEasy get: 'http://files.pharo.org/get-files/70/pharo-win-stable.zip'. However, I can fully download the image through the Internet Browser. The download with Pharo is working: ZnEasy get: 'https://files.pharo.org/'. give me a 200 OK response. Thanks in advance for your help, Cheers, Vincent

Jan. 23, 2018

Cannot debug startUp methods

by Vincent.Blondeau＠lamresearch.com

Hi, In the latest version of Pharo (Build 439 - sha 4810710), I would like to debug a startup script, but when I set up an halt in the method, the image is not able to start anymore... For example, when putting an halt in LanguageEnvironment class>>startUp self halt. self clearDefault. And restarting the image, I got this trace: [0mLanguageEnvironment class>>startUp LanguageEnvironment class(Behavior)>>startUp: ClassSessionHandler>>startup: [ :arg2 | arg2 startup: arg1 ] in WorkingSession>>runStartup: in Block: [ :arg2 | arg2 startup: arg1 ] [ arg2 value: arg3 ] in [ :arg3 | [ arg2 value: arg3 ] on: Exception do: [ :arg4 | self errorHandler handleError: arg4 ] ] in WorkingSession>>runList:do: in Block: [ arg2 value: arg3 ] BlockClosure>>on:do: [ :arg3 | [ arg2 value: arg3 ] on: Exception do: [ :arg4 | self errorHandler handleError: arg4 ] ] in WorkingSession>>runList:do: in Block: [ :arg3 | ... Array(SequenceableCollection)>>do: WorkingSession>>runList:do: WorkingSession>>runStartup: WorkingSession>>start: SessionManager>>launchSnapshot:andQuit: [ tmp3 := self launchSnapshot: arg1 andQuit: arg2. tmp1 signal ] in SessionManager>>snapshot:andQuit: in Block: [ tmp3 := self launchSnapshot: arg1 andQuit: arg2....etc... [ self value. Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... WorkingSession>> runList:do: should have catched the exception and opened the image, but I do not seems too.... What can I do to resolve this issue? I forgot to say that I am under Windows 10 ;) Thanks in advance for your help, Cheers, Vincent

Jan. 23, 2018

Re: [Pharo-dev] [ANN] Next Pharo release moved to end of year

by Stephan Eggermont

Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi all, > > After some analysis of current condition of development, we decided to > move the upcoming release to end of the year (and not May, as usual). Thanks for the clear and timely decision. Having to delay is never nice, but with a high innovation rate comes a higher risk. Denial helps noone, keep up the good work! Stephan

Jan. 23, 2018

[Pharo 7.0-dev] Build #440: 21019 remove mc cache repository classdefault

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #440 was: FAILURE. The Pull Request #696 was integrated: "21019 remove mc cache repository classdefault" Pull request url: https://github.com/pharo-project/pharo/pull/696 Issue Url: https://pharo.fogbugz.com/f/cases/21019 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 23, 2018

[ANN] Next Pharo release moved to end of year

by Esteban Lorenzano

Hi all, After some analysis of current condition of development, we decided to move the upcoming release to end of the year (and not May, as usual). The reason is that we are taking more time than expected to finish/polish a quantity of things that needs to be finish to call this a âsuccessful releaseâ to make us feel confortable with a release early this year. Thing isâ¦ we were very ambitious with this version, because a lot of small pieces get into position and we decided to act. Now, to deliver a good version, we need to finish them. For example, along with all the stabilisation phase we need to operate on P7 (an usual task for every version), we still need to finish this important changes: - fullblocks as default - vm 64bits: stabilise and add win64 - stateful traits - calypso (and nautilus removal) - iceberg: fix the UI We (the core team and the community) have a deep commitment with the progress of Pharo, and we will continue get things right to make the continue improvement a pleasant experience. Say that, expect new announcement of things finished and ready to test next weeks :) cheers! Esteban

Jan. 23, 2018