- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1144: new Method Finder

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

There is a new Pharo build available! The status of the build #1144 was: FAILURE. The Pull Request #1662 was integrated: "new Method Finder" Pull request url: https://github.com/pharo-project/pharo/pull/1662 Issue Url: https://pharo.fogbugz.com/f/cases/finder Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 30, 2018

[Pharo 7.0-dev] Build #1143: 22085 - Fix for infinite debugger

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

There is a new Pharo build available! The status of the build #1143 was: FAILURE. The Pull Request #1621 was integrated: "22085 - Fix for infinite debugger" Pull request url: https://github.com/pharo-project/pharo/pull/1621 Issue Url: https://pharo.fogbugz.com/f/cases/22085 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 30, 2018

[Pharo 7.0-dev] Build #1142: 22251-Open-Repository-with-Monticello-gives-DNU

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

There is a new Pharo build available! The status of the build #1142 was: SUCCESS. The Pull Request #1656 was integrated: "22251-Open-Repository-with-Monticello-gives-DNU" Pull request url: https://github.com/pharo-project/pharo/pull/1656 Issue Url: https://pharo.fogbugz.com/f/cases/22251 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 30, 2018

Re: [Pharo-dev] Esteban's ChangeLog week of 23 July 2018

by Esteban Lorenzano

Hi Nico, > On 30 Jul 2018, at 09:02, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > Hi Esteban, > I encountered this problem a few months ago. > I tried to document FFI with a serie of stackoverflow questions > https://stackoverflow.com/questions/49783882/how-one-deals-with-typedefs-in… <https://stackoverflow.com/questions/49783882/how-one-deals-with-typedefs-in…> > https://stackoverflow.com/questions/49784522/how-one-supports-both-32-and-6… <https://stackoverflow.com/questions/49784522/how-one-supports-both-32-and-6…> Thankfully this is kind of trivial with UFFI (once identified the problem), look at: https://github.com/pharo-project/pharo/pull/1660 <https://github.com/pharo-project/pharo/pull/1660> > > After a deep analysis, I think that FFI needs a serious refactoring (plugin code + image code). Been there, done that :) UFFI is a complete revamp of the image side code. I didnât touch the backend (since our philosophy is to put as much as possible into the image, this was possible) but I think it needs a serious re-think at least in two fields: - basic types needs to be the generic (uint32, uint64, etc.). - external datas have no meaningful use and it adds complexity. - callback logic needs to be moved from Alien to FFI > But I have stopped that work in the middle... (no time available for a few months). > The next thing I wanted to do is to study all your efforts with UFFI, and how you found workarounds for other pitfalls like > https://stackoverflow.com/questions/49784253/how-one-deals-with-multiple-po… <https://stackoverflow.com/questions/49784253/how-one-deals-with-multiple-po…> > https://stackoverflow.com/questions/49783443/how-one-defines-a-fixed-size-a… <https://stackoverflow.com/questions/49783443/how-one-defines-a-fixed-size-a…> > https://stackoverflow.com/questions/49783126/how-one-defines-a-union-type-i… <https://stackoverflow.com/questions/49783126/how-one-defines-a-union-type-i…> > https://stackoverflow.com/questions/49782651/how-one-aligns-structure-field… <https://stackoverflow.com/questions/49782651/how-one-aligns-structure-field…> Solved in UFFI. Cheers, Esteban > > Cheers > > > 2018-07-30 8:00 GMT+02:00 <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > Hello! > > This is my weekly ChangeLog, from 23 July 2018 to 29 July 2018. > You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=23/7/2018&to=29/7/2018 <http://log.smallworks.eu/web/search?from=23/7/2018&to=29/7/2018> > > ChangeLog > ========= > > 27 July 2018: > ------------- > > * I found a problem that was making win64 bit version to crash: size_t implementation on UFFI was not resolving properly there (since it was mapped to a long, which is not correct on win64 architecture). > > To fix it, I changed FFISizeT type to work as FFILong, with different "real types" depending on architecture. > > Now, there is a problem to solve because structures using this type (like +LGitStringArray+) need to be regenerated, which may generate some difficulties... will see. > > > 23 July 2018: > ------------- > > * So well. Spent the full day debugging libgit2 without symbol information :( > > There is some problem with adding paths to an index and I still cannot figure out what's the problem. > > I'll continue trying tomorrow. > > > cheers! > Esteban > >

July 30, 2018

[Pharo 7.0-dev] Build #1141: 22089-Integrate-new-Calypso-0115

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

There is a new Pharo build available! The status of the build #1141 was: FAILURE. The Pull Request #1507 was integrated: "22089-Integrate-new-Calypso-0115" Pull request url: https://github.com/pharo-project/pharo/pull/1507 Issue Url: https://pharo.fogbugz.com/f/cases/22089 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 30, 2018

Re: [Pharo-dev] Esteban's ChangeLog week of 23 July 2018

by Nicolas Cellier

Hi Esteban, I encountered this problem a few months ago. I tried to document FFI with a serie of stackoverflow questions https://stackoverflow.com/questions/49783882/how-one-deals-with-typedefs-in… https://stackoverflow.com/questions/49784522/how-one-supports-both-32-and-6… After a deep analysis, I think that FFI needs a serious refactoring (plugin code + image code). But I have stopped that work in the middle... (no time available for a few months). The next thing I wanted to do is to study all your efforts with UFFI, and how you found workarounds for other pitfalls like https://stackoverflow.com/questions/49784253/how-one-deals-with-multiple-po… https://stackoverflow.com/questions/49783443/how-one-defines-a-fixed-size-a… https://stackoverflow.com/questions/49783126/how-one-defines-a-union-type-i… https://stackoverflow.com/questions/49782651/how-one-aligns-structure-field… Cheers 2018-07-30 8:00 GMT+02:00 <estebanlm(a)gmail.com>: > Hello! > > This is my weekly ChangeLog, from 23 July 2018 to 29 July 2018. > You can see it in a better format by going here: > http://log.smallworks.eu/web/search?from=23/7/2018&to=29/7/2018 > > ChangeLog > ========= > > 27 July 2018: > ------------- > > * I found a problem that was making win64 bit version to crash: size_t > implementation on UFFI was not resolving properly there (since it was > mapped to a long, which is not correct on win64 architecture). > > To fix it, I changed FFISizeT type to work as FFILong, with different > "real types" depending on architecture. > > Now, there is a problem to solve because structures using this type > (like +LGitStringArray+) need to be regenerated, which may generate some > difficulties... will see. > > > 23 July 2018: > ------------- > > * So well. Spent the full day debugging libgit2 without symbol > information :( > > There is some problem with adding paths to an index and I still cannot > figure out what's the problem. > > I'll continue trying tomorrow. > > > cheers! > Esteban > >

July 30, 2018

Esteban's ChangeLog week of 23 July 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 23 July 2018 to 29 July 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=23/7/2018&to=29/7/2018 ChangeLog ========= 27 July 2018: ------------- * I found a problem that was making win64 bit version to crash: size_t implementation on UFFI was not resolving properly there (since it was mapped to a long, which is not correct on win64 architecture). To fix it, I changed FFISizeT type to work as FFILong, with different "real types" depending on architecture. Now, there is a problem to solve because structures using this type (like +LGitStringArray+) need to be regenerated, which may generate some difficulties... will see. 23 July 2018: ------------- * So well. Spent the full day debugging libgit2 without symbol information :( There is some problem with adding paths to an index and I still cannot figure out what's the problem. I'll continue trying tomorrow. cheers! Esteban

July 30, 2018

Charting in Roassal2

by Shaping

Hi Folks. Can anyone tell me whether we have candlestick-charting ability in Roassal2? Shaping

July 28, 2018

[Pharo 7.0-dev] Build #1139: 22126-allInstVarNames-returns-wrong-results-for-classes-with-stateful-traits

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

There is a new Pharo build available! The status of the build #1139 was: SUCCESS. The Pull Request #1530 was integrated: "22126-allInstVarNames-returns-wrong-results-for-classes-with-stateful-traits" Pull request url: https://github.com/pharo-project/pharo/pull/1530 Issue Url: https://pharo.fogbugz.com/f/cases/22126 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 27, 2018

[Pharo 7.0-dev] Build #1138: 22273-When-there-is-a-duplicated-instance-variable-it-is-created-always

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

There is a new Pharo build available! The status of the build #1138 was: SUCCESS. The Pull Request #1643 was integrated: "22273-When-there-is-a-duplicated-instance-variable-it-is-created-always" Pull request url: https://github.com/pharo-project/pharo/pull/1643 Issue Url: https://pharo.fogbugz.com/f/cases/22273 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 27, 2018