- Pharo-dev - lists.pharo.org

Zerconf download of source files in Pharo 7

by Torsten Bergmann

When I run wget -O- get.pharo.org/70+vm | bash the zeroconf script downloads image bundle, VM bundle and sources archive: -------------------------------------------------------------------- Downloading the latest 70 Image: http://files.pharo.org/get-files/70/pharo.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/get-files/70/pharo-linux-stable.zip pharo-vm/pharo Downloading PharoV70.sources: http://files.pharo.org/get-files/70/sources.zip Creating starter scripts pharo and pharo-ui ... -------------------------------------------------------------------- Now in Pharo 7 the pharo.zip already includes the sources. Right? See attached screenshot. So why is the zeroconf additionally downloading the sources.zip which IMHO is an unnecessary additional download now. Maybe because it was necessary in the past and the zeroconf was not adopted. Anyone able to check and maybe remove the additional download for Pharo 7? Thx T.

Oct. 19, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by Guillermo Polito

On Thu, Oct 19, 2017 at 1:36 AM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > Thanks Guille, now it looks fine. > > Another issue for Windows users is that you cannot execute the workaround: > > $ git config core.longpaths true > > until you first cloned the repository. That's why I said one first should > let fail the git clone command and then: > > $ cd pharo/ > $ git config core.longpaths true > $ git checkout -f HEAD > > If anyone can check because submitting a fix should be easy and there > shouldn't be guessing in the process. > If a windows user confirms, I update it. I don't have access to a windows machine right now :). > > Cheers, > > HernÃ¡n > > > 2017-10-18 4:37 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> >> >> On Tue, Oct 17, 2017 at 12:42 PM, HernÃ¡n Morales Durand < >> hernan.morales(a)gmail.com> wrote: >> >>> Thank you Esteban, that was the problem! :) >>> >>> Maybe guille wants to clarify the correct remote repository in the page: >>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>> ribute-a-fix-to-Pharo after "You can click on the *Add remote* option >>> and configure a remote with a name and repository url." >>> >> >> Done that. >> >> Can you check if that's ok? >> >> >>> >>> Another thing. I created a PR with a fix for this bug : >>> https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-RadioB >>> uttonModel-ignore-disable following the guide to the Step 3. However I >>> couldn't view any PR in my Github page (see attach). >>> >>> Do I miss something? >>> >>> >>> 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> no is ok. >>>> with the pharo version I know the iceberg version :) >>>> >>>> anyway your problem is that the remote for pharo is bad. >>>> >>>> you added git@github.com:pharo/pharo.git and I do not think that >>>> exists. >>>> Correct one is: >>>> >>>> git@github.com:pharo-project/pharo.git >>>> >>>> Esteban >>>> >>>> >>>> On 17 Oct 2017, at 11:51, HernÃ¡n Morales Durand < >>>> hernan.morales(a)gmail.com> wrote: >>>> >>>> I don't see any easy way to find the Iceberg version. >>>> >>>> Should I update Iceberg using this script also in Pharo 7? >>>> >>>> "Restore defaults" >>>> Iceberg enableMetacelloIntegration: false. >>>> MetacelloPharo30Platform select. >>>> >>>> "Update metacello" >>>> Metacello new >>>> baseline: 'Metacello'; >>>> repository: 'github://metacello/metacello:Pharo6.1/repository'; >>>> onConflict: [:e | e useIncoming ]; >>>> get; >>>> load. >>>> >>>> "Update iceberg" >>>> #( >>>> 'Iceberg-UI' >>>> 'Iceberg-Plugin-GitHub' >>>> 'Iceberg-Plugin' >>>> 'Iceberg-Metacello-Integration' >>>> 'Iceberg-Libgit-Tonel' >>>> 'Iceberg-Libgit-Filetree' >>>> 'Iceberg-Libgit' >>>> 'Iceberg' >>>> 'LibGit-Core') >>>> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: >>>> #removeFromSystem ]. >>>> Metacello new >>>> baseline: 'Iceberg'; >>>> repository: 'github://pharo-vcs/iceberg:v0.6'; >>>> load. >>>> >>>> 2017-10-17 6:46 GMT-03:00 HernÃ¡n Morales Durand < >>>> hernan.morales(a)gmail.com>: >>>> >>>>> Hi Esteban, >>>>> >>>>> This one: >>>>> >>>>> wget -O- get.pharo.org/70+vm | bash - >>>>> >>>>> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>> >>>>>> which Pharo version (and Iceberg version) do you have? >>>>>> >>>>>> Esteban >>>>>> >>>>>> On 17 Oct 2017, at 04:36, HernÃ¡n Morales Durand < >>>>>> hernan.morales(a)gmail.com> wrote: >>>>>> >>>>>> Hi Guille, >>>>>> >>>>>> In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>>>>> ribute-a-fix-to-Pharo >>>>>> >>>>>> This part is not working for me: "Go back to iceberg, right click on >>>>>> the pharo repository and go to the *Pharo* entry. You'll see the >>>>>> option *Create new branch from Fogbugz issue*." >>>>>> >>>>>> Because there is no such "Pharo" option in the menu. See the attached >>>>>> screenshot. >>>>>> >>>>>> Did I miss something? >>>>>> Any suggestion? >>>>>> >>>>>> >>>>>> 2017-08-10 12:17 GMT-03:00 Guillermo Polito < >>>>>> guillermopolito(a)gmail.com>: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I've made some write up for the pharo part (not metacello or >>>>>>> external projects) >>>>>>> >>>>>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>>>>>> ribute-a-fix-to-Pharo >>>>>>> >>>>>>> Of course, expect bugs on it :) Not everything is smooth. If you >>>>>>> have comments, they are welcome. >>>>>>> >>>>>>> Guille >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Guille Polito >>>>>>> >>>>>>> Research Engineer >>>>>>> French National Center for Scientific Research - >>>>>>> *http://www.cnrs.fr* <http://www.cnrs.fr/> >>>>>>> >>>>>>> >>>>>>> *Web:* *http://guillep.github.io* <http://guillep.github.io/> >>>>>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>>>>>> >>>>>> >>>>>> <Clipboard01.png> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> French National Center for Scientific Research - *http://www.cnrs.fr >> <http://www.cnrs.fr>* >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >> > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Oct. 19, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by Esteban Lorenzano

Hi, > On 19 Oct 2017, at 01:36, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Thanks Guille, now it looks fine. > > Another issue for Windows users is that you cannot execute the workaround: > > $ git config core.longpaths true > > until you first cloned the repository. That's why I said one first should let fail the git clone command and then: > > $ cd pharo/ > $ git config core.longpaths true > $ git checkout -f HEAD > > If anyone can check because submitting a fix should be easy and there shouldn't be guessing in the process. thatâs why we created tonel (we will be moving to it soon). libgit2 does not recognise core.longpaths (in iceberg, process is split in two: bare clone and checkout so I tried adding that option when repository is created before checking out and it does not works either). also, one other reason to move to tonel is time: clone itself is very fast, but the checkout (there is a ridiculous amount of files to recreate there) is very slow. Esteban > > Cheers, > > HernÃ¡n > > > 2017-10-18 4:37 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>: > > > On Tue, Oct 17, 2017 at 12:42 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: > Thank you Esteban, that was the problem! :) > > Maybe guille wants to clarify the correct remote repository in the page: https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… <https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to…> after "You can click on the Add remote option and configure a remote with a name and repository url." > > Done that. > > Can you check if that's ok? > > > Another thing. I created a PR with a fix for this bug : https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-RadioButtonModel-igno… <https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-RadioButtonModel-igno…> following the guide to the Step 3. However I couldn't view any PR in my Github page (see attach). > > Do I miss something? > > > 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > no is ok. > with the pharo version I know the iceberg version :) > > anyway your problem is that the remote for pharo is bad. > > you added git(a)github.com <mailto:git@github.com>:pharo/pharo.git and I do not think that exists. > Correct one is: > > git(a)github.com <mailto:git@github.com>:pharo-project/pharo.git > > Esteban > > >> On 17 Oct 2017, at 11:51, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: >> >> I don't see any easy way to find the Iceberg version. >> >> Should I update Iceberg using this script also in Pharo 7? >> >> "Restore defaults" >> Iceberg enableMetacelloIntegration: false. >> MetacelloPharo30Platform select. >> >> "Update metacello" >> Metacello new >> baseline: 'Metacello'; >> repository: 'github://metacello/metacello:Pharo6.1/repository <>'; >> onConflict: [:e | e useIncoming ]; >> get; >> load. >> >> "Update iceberg" >> #( >> 'Iceberg-UI' >> 'Iceberg-Plugin-GitHub' >> 'Iceberg-Plugin' >> 'Iceberg-Metacello-Integration' >> 'Iceberg-Libgit-Tonel' >> 'Iceberg-Libgit-Filetree' >> 'Iceberg-Libgit' >> 'Iceberg' >> 'LibGit-Core') >> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem ]. >> Metacello new >> baseline: 'Iceberg'; >> repository: 'github://pharo-vcs/iceberg:v0.6 <>'; >> load. >> >> 2017-10-17 6:46 GMT-03:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>>: >> Hi Esteban, >> >> This one: >> >> wget -O- get.pharo.org/70+vm <http://get.pharo.org/70+vm> | bash - >> >> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> which Pharo version (and Iceberg version) do you have? >> >> Esteban >> >>> On 17 Oct 2017, at 04:36, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: >>> >>> Hi Guille, >>> >>> In https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… <https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to…> >>> >>> This part is not working for me: "Go back to iceberg, right click on the pharo repository and go to the Pharo entry. You'll see the option Create new branch from Fogbugz issue." >>> >>> Because there is no such "Pharo" option in the menu. See the attached screenshot. >>> >>> Did I miss something? >>> Any suggestion? >>> >>> >>> 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>: >>> Hi, >>> >>> I've made some write up for the pharo part (not metacello or external projects) >>> >>> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… <https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to…> >>> >>> Of course, expect bugs on it :) Not everything is smooth. If you have comments, they are welcome. >>> >>> Guille >>> >>> -- >>> >>> Guille Polito >>> >>> Research Engineer >>> French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> >>> >>> >>> Web: http://guillep.github.io <http://guillep.github.io/> >>> Phone: +33 06 52 70 66 13 <tel:+33%206%2052%2070%2066%2013> >>> <Clipboard01.png> >> >> >> > > > > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13 >

Oct. 19, 2017

Re: [Pharo-dev] UnifiedFFI Docs

by Ben Coman

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/ >> PharoBookWorkInProgress/lastSuccessfulBuild/artifact/ >> book-result/UnifiedFFI/UnifiedFFI.pdf >> >> >> >> https://github.com/SquareBracketAssociates/Booklet-uFFI >> >> >> >> has a link to a bintray pdf download >> >> >> >> Stephan >> >> >> >> >> >> >> > >> > >> >> >

Oct. 19, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by HernÃ¡n Morales Durand

Thanks Guille, now it looks fine. Another issue for Windows users is that you cannot execute the workaround: $ git config core.longpaths true until you first cloned the repository. That's why I said one first should let fail the git clone command and then: $ cd pharo/ $ git config core.longpaths true $ git checkout -f HEAD If anyone can check because submitting a fix should be easy and there shouldn't be guessing in the process. Cheers, HernÃ¡n 2017-10-18 4:37 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: > > > On Tue, Oct 17, 2017 at 12:42 PM, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > >> Thank you Esteban, that was the problem! :) >> >> Maybe guille wants to clarify the correct remote repository in the page: >> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >> ribute-a-fix-to-Pharo after "You can click on the *Add remote* option >> and configure a remote with a name and repository url." >> > > Done that. > > Can you check if that's ok? > > >> >> Another thing. I created a PR with a fix for this bug : >> https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-RadioB >> uttonModel-ignore-disable following the guide to the Step 3. However I >> couldn't view any PR in my Github page (see attach). >> >> Do I miss something? >> >> >> 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> no is ok. >>> with the pharo version I know the iceberg version :) >>> >>> anyway your problem is that the remote for pharo is bad. >>> >>> you added git@github.com:pharo/pharo.git and I do not think that >>> exists. >>> Correct one is: >>> >>> git@github.com:pharo-project/pharo.git >>> >>> Esteban >>> >>> >>> On 17 Oct 2017, at 11:51, HernÃ¡n Morales Durand < >>> hernan.morales(a)gmail.com> wrote: >>> >>> I don't see any easy way to find the Iceberg version. >>> >>> Should I update Iceberg using this script also in Pharo 7? >>> >>> "Restore defaults" >>> Iceberg enableMetacelloIntegration: false. >>> MetacelloPharo30Platform select. >>> >>> "Update metacello" >>> Metacello new >>> baseline: 'Metacello'; >>> repository: 'github://metacello/metacello:Pharo6.1/repository'; >>> onConflict: [:e | e useIncoming ]; >>> get; >>> load. >>> >>> "Update iceberg" >>> #( >>> 'Iceberg-UI' >>> 'Iceberg-Plugin-GitHub' >>> 'Iceberg-Plugin' >>> 'Iceberg-Metacello-Integration' >>> 'Iceberg-Libgit-Tonel' >>> 'Iceberg-Libgit-Filetree' >>> 'Iceberg-Libgit' >>> 'Iceberg' >>> 'LibGit-Core') >>> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: >>> #removeFromSystem ]. >>> Metacello new >>> baseline: 'Iceberg'; >>> repository: 'github://pharo-vcs/iceberg:v0.6'; >>> load. >>> >>> 2017-10-17 6:46 GMT-03:00 HernÃ¡n Morales Durand < >>> hernan.morales(a)gmail.com>: >>> >>>> Hi Esteban, >>>> >>>> This one: >>>> >>>> wget -O- get.pharo.org/70+vm | bash - >>>> >>>> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>> >>>>> which Pharo version (and Iceberg version) do you have? >>>>> >>>>> Esteban >>>>> >>>>> On 17 Oct 2017, at 04:36, HernÃ¡n Morales Durand < >>>>> hernan.morales(a)gmail.com> wrote: >>>>> >>>>> Hi Guille, >>>>> >>>>> In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>>>> ribute-a-fix-to-Pharo >>>>> >>>>> This part is not working for me: "Go back to iceberg, right click on >>>>> the pharo repository and go to the *Pharo* entry. You'll see the >>>>> option *Create new branch from Fogbugz issue*." >>>>> >>>>> Because there is no such "Pharo" option in the menu. See the attached >>>>> screenshot. >>>>> >>>>> Did I miss something? >>>>> Any suggestion? >>>>> >>>>> >>>>> 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com >>>>> >: >>>>> >>>>>> Hi, >>>>>> >>>>>> I've made some write up for the pharo part (not metacello or external >>>>>> projects) >>>>>> >>>>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>>>>> ribute-a-fix-to-Pharo >>>>>> >>>>>> Of course, expect bugs on it :) Not everything is smooth. If you have >>>>>> comments, they are welcome. >>>>>> >>>>>> Guille >>>>>> >>>>>> -- >>>>>> >>>>>> Guille Polito >>>>>> >>>>>> Research Engineer >>>>>> French National Center for Scientific Research - *http://www.cnrs.fr* >>>>>> <http://www.cnrs.fr/> >>>>>> >>>>>> >>>>>> *Web:* *http://guillep.github.io* <http://guillep.github.io/> >>>>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>>>>> >>>>> >>>>> <Clipboard01.png> >>>>> >>>>> >>>>> >>>> >>> >>> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 >

Oct. 18, 2017

Re: [Pharo-dev] UnifiedFFI Docs

by Todd Blanchard

> On Oct 18, 2017, at 1:21 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > <snip> > > Should isNull be defined as you suggest in ByteArray? If the semantic is #isNullPointer, then I don't think so. If it's a more general message, then maybe... > > What is the class of handle? It is ByteArray. I agree that ByteArray responding to isNull is weird. The struct the memory maps is struct { void* data, int flags } so I can work around this with something like self data ifNil: [.....] I have just encountered another problem. Ben creates a type specification as a class variable to model void*[3] VoidPointer3 := FFITypeArray ofType: 'void*' size: 3. which produces the following accessor for data (FFITypeArray ofType: #FFIVoid size: 3) fromHandle: (handle copyFrom: OFFSET_DATA to: OFFSET_DATA + 23) This fails because the native size of void is undefined even though it is a void* being mapped. I will continue to see if I can figure out why it generates this spec - definitely a broken assumption somewhere in here. -Todd Blanchard

Oct. 18, 2017

Re: [Pharo-dev] UnifiedFFI Docs

by Nicolas Cellier

2017-10-18 19:05 GMT+02:00 Todd Blanchard <tblanchard(a)mac.com>: > I'm working through Ben's great blog post about playing with libclang and > I am puzzled by something. > > 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? > > > In original FFI, a ByteArray could not represent a pointer, so it answered: ByteArray>>isNull "Answer false since only external addresses can be null" ^false There was an ExternalAddress subclass for this purpose where isNull was defined: ExternalAddress>>isNull "Answer true if I am a null pointer" 1 to: self size do:[:i| (self at: i) = 0 ifFalse:[^false]]. ^true and there was also a #beNull to nullify the address... What happens now with UnifiedFFI, is the old FFI API supported (and thus the example correct), what about Alien, are questions that you must inquire, but once upon a time, it worked. Should isNull be defined as you suggest in ByteArray? If the semantic is #isNullPointer, then I don't think so. If it's a more general message, then maybe... What is the class of handle? > 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/ >> PharoBookWorkInProgress/lastSuccessfulBuild/artifact/ >> book-result/UnifiedFFI/UnifiedFFI.pdf >> >> >> >> https://github.com/SquareBracketAssociates/Booklet-uFFI >> >> >> >> has a link to a bintray pdf download >> >> >> >> Stephan >> >> >> >> >> >> >> > >> > >> >> >

Oct. 18, 2017

Re: [Pharo-dev] UnifiedFFI Docs

by Todd Blanchard

I'm working through Ben's great blog post about playing with libclang and I am puzzled by something. 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 <mailto:stepharo.self@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 <mailto:tblanchard@mac.com>> wrote: > > Wonderful! Thanks. > > > >> On Oct 17, 2017, at 3:45 PM, stephan <stephan(a)stack.nl <mailto:stephan@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://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…> > >> > >> https://github.com/SquareBracketAssociates/Booklet-uFFI <https://github.com/SquareBracketAssociates/Booklet-uFFI> > >> > >> has a link to a bintray pdf download > >> > >> Stephan > >> > >> > >> > > > > >

Oct. 18, 2017

Re: [Pharo-dev] open street map

by Pavel Krivanek

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. 18, 2017

open street map

by Stephane Ducasse

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. 18, 2017