October 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] UnifiedFFI Docs

by Todd Blanchard

Thatâs great - itâs been kind of magical but a couple things have changed since you wrote it and some bugs have crept into ffi. Right now Iâm finding the generated accessor for the VoidPointer3 is actually generating a void 3 accessor and that doesnât work. I spent all day yesterday tracking it to the accessor generating code. Sent from the road > On Oct 18, 2017, at 22:29, Ben Coman <btc(a)openinworld.com> wrote: > > > >> On Thu, Oct 19, 2017 at 1:05 AM, Todd Blanchard <tblanchard(a)mac.com> wrote: >> I'm working through Ben's great blog post about playing with libclang and I am puzzled by something. > > Thx Todd. Knowing someone is looking at it encourages me to expand it. > I'm interested in looking at your specific questions, but it might not be until next week after this stint of long work days. > > cheers -ben > > >> >> invalidateSessionData >> handle atAllPut: 0. >> >> zero;s out the handle. Cool. However, >> >> handle isNull >> >> does not return true despite it being used in the getString method as >> >> ^ handle isNull >> ifTrue: ['external memory invalidated by session restart'] >> ifFalse:[LibClang clang_getCString__cxString: self]. >> >> Looks like there should be an isNull on ByteArray that returns true if all bytes are zero but it isn't there. Was it dropped for some reason? >> >> >> >>> On Oct 18, 2017, at 2:58 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: >>> >>> Sure the documentation could be better, that is definetly important, but is already good enough and UFFI is a very technical subject much more suited to a mailing list . Its not physical possible to cover the massive potential of UFFI. >>> >>> On Wed, Oct 18, 2017 at 9:32 AM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>> Please do not hesitate to do Pull Requests. >>>> Luc told me that he wants to do a pass on it and Esteban promises that to me >>>> but he is super busy. >>>> >>>> Stef >>>> >>>> >>>> On Wed, Oct 18, 2017 at 5:54 AM, Todd Blanchard <tblanchard(a)mac.com> wrote: >>>> > Wonderful! Thanks. >>>> > >>>> >> On Oct 17, 2017, at 3:45 PM, stephan <stephan(a)stack.nl> wrote: >>>> >> >>>> >> On 17-10-17 23:06, Todd Blanchard wrote: >>>> >>> Anyone know what happened to this? >>>> >>> https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… >>>> >> >>>> >> https://github.com/SquareBracketAssociates/Booklet-uFFI >>>> >> >>>> >> has a link to a bintray pdf download >>>> >> >>>> >> Stephan >>>> >> >>>> >> >>>> >> >>>> > >>>> > >>>> >> >

Oct. 19, 2017

Re: [Pharo-dev] open street map

by Stephane Ducasse

Tx pavel. On Wed, Oct 18, 2017 at 5:15 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > probably coordinates. This works: > http://a.tile.openstreetmap.org/8/129/88.png > > -- Pavel > > > 2017-10-18 17:04 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> Hi guys >> >> in the mooc I was used to use this expression >> >> http://a.tile.openstreetmap.org/8/12/8.png >> >> and now I get an empty tile and I wonder why. May openstreet map changed >> their policy. >> >> Did any of you experience the same? >> >> Stef >> >

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by Stephane Ducasse

I would suggest to load pillar based on version and stable version. I never try development especially because I'm maintaining branches in MC which does not support branches. Setf On Thu, Oct 19, 2017 at 12:05 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Steph, > > On 19 October 2017 at 11:56, stephan <stephan(a)stack.nl> wrote: >> Iceberg enableMetacelloIntegration: true. >> Metacello new >> baseline: 'GToolkit'; >> repository: 'github://feenkcom/gtoolkit/src'; >> load. >> >> tries to resolve ConfigurationOfGrease to #release1 >> >> Stephan > > I've hit exactly the same issue. > > It looks like ConfigurationOfGrease is missing #pharo7.x version > identifiers throughout it. > > I took a guess at the required changes (in the attached file), but > have hit several other problems with Pillar that I'm still working > through, e.g. at the start of October, loading Pillar with: > > > spec > project: 'Pillar' with: [ > spec > className: #ConfigurationOfPillar; > versionString: #'development'; > repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main' ]. > > > loaded Grease-Pharo30-Core. But now it doesn't. > > > Cheers, > Alistair

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by Stephane Ducasse

Hi About pillar I'm working on it. Now I only maintain two versions one for Pharo 50 and one for Pharo 60. The new things are happening in Pharo 60. Now this was a bad idea to link Pillar with Magritte only to manage configurations because Magritte is too big to me and full of too many constraints like loading Grease and others. I do not want to spend my time fighting with issues imposed to me. I'm slowly working on freeing Pillar from Magritte but I got stuck and out of energy. Now I will not maintain a version for Pharo 70 alpha because I simply cannot. Stef On Thu, Oct 19, 2017 at 12:05 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Steph, > > On 19 October 2017 at 11:56, stephan <stephan(a)stack.nl> wrote: >> Iceberg enableMetacelloIntegration: true. >> Metacello new >> baseline: 'GToolkit'; >> repository: 'github://feenkcom/gtoolkit/src'; >> load. >> >> tries to resolve ConfigurationOfGrease to #release1 >> >> Stephan > > I've hit exactly the same issue. > > It looks like ConfigurationOfGrease is missing #pharo7.x version > identifiers throughout it. > > I took a guess at the required changes (in the attached file), but > have hit several other problems with Pillar that I'm still working > through, e.g. at the start of October, loading Pillar with: > > > spec > project: 'Pillar' with: [ > spec > className: #ConfigurationOfPillar; > versionString: #'development'; > repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main' ]. > > > loaded Grease-Pharo30-Core. But now it doesn't. > > > Cheers, > Alistair

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by stephan

On 19-10-17 14:23, Aliaksei Syrel wrote: > Something changed in Pharo 7 between 06.10.2017 - 17.10.2017 because > GToolkit it loads flawlessly in Pharo from 6th of October. Looks most likely to be build 197: There is a new Pharo build available! The status of the build #197 was: SUCCESS. The Pull Request #362 was integrated: "20540-move-metacelloPlatformAttributes-to-Pharo7" Pull request url: https://github.com/pharo-project/pharo/pull/362 Issue Url: https://pharo.fogbugz.com/f/cases/20540 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by Aliaksei Syrel

Hi In last two commits I tried to fix Baseline of Documenter but failed because of Pillar. See screenshot. [image: Inline images 1] For a very long time we depended on #development of Pillar, but suddenly it gone away. See screenshot. [image: Inline images 2] I will change #pier back to #development. Something changed in Pharo 7 between 06.10.2017 - 17.10.2017 because GToolkit it loads flawlessly in Pharo from 6th of October.

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by stephan

On 19-10-17 13:32, Alistair Grant wrote: > That loads successfully for me, thanks, but Pillar & Magritte are > broken in new and interesting ways. It will be a while before I can > look in to it properly. The #pier and Magritte 3.5.0 references are not helpful there, and it looks like there are more pharo7 tags missing Stephan

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by Alistair Grant

Hi Stephan, On 19 October 2017 at 12:45, stephan <stephan(a)stack.nl> wrote: > On 19-10-17 12:21, stephan wrote: >> >> On 19-10-17 12:05, Alistair Grant wrote: >> >>> I've hit exactly the same issue. >>> >>> It looks like ConfigurationOfGrease is missing #pharo7.x version >>> identifiers throughout it. > > > Name: ConfigurationOfGrease-StephanEggermont.347 > Author: StephanEggermont > Time: 19 October 2017, 12:42:22.848053 pm > UUID: baaf8ebf-4518-0d00-ab4f-cad309d94048 > Ancestors: ConfigurationOfGrease-JohanBrichau.346 > > Added Pharo 7 versions of release1/1.3 That loads successfully for me, thanks, but Pillar & Magritte are broken in new and interesting ways. It will be a while before I can look in to it properly. Thanks, Alistair

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by stephan

On 19-10-17 12:21, stephan wrote: > On 19-10-17 12:05, Alistair Grant wrote: > >> I've hit exactly the same issue. >> >> It looks like ConfigurationOfGrease is missing #pharo7.x version >> identifiers throughout it. Name: ConfigurationOfGrease-StephanEggermont.347 Author: StephanEggermont Time: 19 October 2017, 12:42:22.848053 pm UUID: baaf8ebf-4518-0d00-ab4f-cad309d94048 Ancestors: ConfigurationOfGrease-JohanBrichau.346 Added Pharo 7 versions of release1/1.3

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by stephan

On 19-10-17 12:05, Alistair Grant wrote: > I've hit exactly the same issue. > > It looks like ConfigurationOfGrease is missing #pharo7.x version > identifiers throughout it. BaselineOfGToolkitDocumenter refers to ConfigurationOfPillar #pier version. That is very, very old. Pillar broke compatibility years ago ConfigurationOfPillar does not look good at all: - no pharo 7 in stable, and a strange common version. - in the stable version 6.0.6 all dependencies are to numbered versions instead of symbolic ones. ConfigurationOfCocoon has the same problem, pointing to Magritte3 3.5.0 I could load by defining #'pharo7' versions in #'release1' and #'release1.3' Stephan

Oct. 19, 2017