- Pharo-users - lists.pharo.org

Re: [Pharo-users] UFFI can not generate Structure accessor of type char[100]

by Dimitris Chloupis

then great work^2 Do you want me to add this information to the UFFI documentation ? Probably I will also add some more examples for handles, pointers etc. I assume this is the repo for the docs of UFFI https://github.com/SquareBracketAssociates/PharoInProgress correct ? On Tue, Nov 8, 2016 at 2:12 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > On 8 Nov 2016, at 12:55, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > Thank you Esteban > > By the way I really love the design of UFFI , very clean and quite easy to > understand , great work to you and Igor :) > > > UFFI is just mine ;) > (but I sanded in giant shoulders as I took Igor work as inspirationâ¦ and > to âborrowâ many cool ideas) > > Esteban > > > On Tue, Nov 8, 2016 at 1:54 PM Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > On 8 Nov 2016, at 12:49, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > I was reaching a similar conclusion > > Currently I have a void pointer to the struct with the members I mentioned > > I can get char[100] > > pointerToStruct fromCString > > and I can get the int with > > pointerToStruct getHandle integerAt: 101 size:4 signed: false > > so if I want to pass the address of the pointer to my YourStruct instance > will I have to initialize with > > YourStruct fromHandler: (pointerToStruct getHandle) > > is this a correct and safe way to pass the address ? > > > yes. > > Esteban > > > > On Tue, Nov 8, 2016 at 1:21 PM Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > it never could. > you need to do a âspecial typeâ, who has to be something like: > > YourStruct class>>initialize > Char100 := FFITypeArray ofType: #char. > > fieldsDesc > ^ #( > Char100 data; > int count; > ) > > but thenâ¦ you want to optimise that and in field accessors, who will look > something like this: > > YourStruct >>data > "This method was automatically generated" > ^(FFITypeArray ofType: #char size: 100) fromHandle: (handle > copyFrom: 1 to: 100) > > you can change that for: > > YourStruct >>data > "This method was automatically generated" > ^Char100 fromHandle: (handle copyFrom: 1 to: 100) > > and same for setter. > (other way will work, but it will be suboptimal) > > Esteban > > > On 8 Nov 2016, at 12:10, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > > > I have FFIExternalStructure which has at class side > > > > fieldsDesc > > ^#( > > char data[100]; > > int count; > > ) > > > > if I try to do > > > > EphCPPTestStructure rebuildFieldAccessors . > > > > in order to generate the accessors for the members of the struct it > complains with an error that it does not recognise the type of " [ " > > > > Does that mean that char arrays are other arrays are not supported as > struct members or will I have to do this manually ? > > > >

Nov. 8, 2016

Re: [Pharo-users] UFFI can not generate Structure accessor of type char[100]

by Esteban Lorenzano

> On 8 Nov 2016, at 12:55, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > Thank you Esteban > > By the way I really love the design of UFFI , very clean and quite easy to understand , great work to you and Igor :) UFFI is just mine ;) (but I sanded in giant shoulders as I took Igor work as inspirationâ¦ and to âborrowâ many cool ideas) Esteban > > On Tue, Nov 8, 2016 at 1:54 PM Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> On 8 Nov 2016, at 12:49, Dimitris Chloupis <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: >> >> I was reaching a similar conclusion >> >> Currently I have a void pointer to the struct with the members I mentioned >> >> I can get char[100] >> >> pointerToStruct fromCString >> >> and I can get the int with >> >> pointerToStruct getHandle integerAt: 101 size:4 signed: false >> >> so if I want to pass the address of the pointer to my YourStruct instance will I have to initialize with >> >> YourStruct fromHandler: (pointerToStruct getHandle) >> >> is this a correct and safe way to pass the address ? > > yes. > > Esteban > >> >> >> On Tue, Nov 8, 2016 at 1:21 PM Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> it never could. >> you need to do a âspecial typeâ, who has to be something like: >> >> YourStruct class>>initialize >> Char100 := FFITypeArray ofType: #char. >> >> fieldsDesc >> ^ #( >> Char100 data; >> int count; >> ) >> >> but thenâ¦ you want to optimise that and in field accessors, who will look something like this: >> >> YourStruct >>data >> "This method was automatically generated" >> ^(FFITypeArray ofType: #char size: 100) fromHandle: (handle copyFrom: 1 to: 100) >> >> you can change that for: >> >> YourStruct >>data >> "This method was automatically generated" >> ^Char100 fromHandle: (handle copyFrom: 1 to: 100) >> >> and same for setter. >> (other way will work, but it will be suboptimal) >> >> Esteban >> >> > On 8 Nov 2016, at 12:10, Dimitris Chloupis <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: >> > >> > I have FFIExternalStructure which has at class side >> > >> > fieldsDesc >> > ^#( >> > char data[100]; >> > int count; >> > ) >> > >> > if I try to do >> > >> > EphCPPTestStructure rebuildFieldAccessors . >> > >> > in order to generate the accessors for the members of the struct it complains with an error that it does not recognise the type of " [ " >> > >> > Does that mean that char arrays are other arrays are not supported as struct members or will I have to do this manually ? >> >>

Nov. 8, 2016

Re: [Pharo-users] UFFI can not generate Structure accessor of type char[100]

by Dimitris Chloupis

Thank you Esteban By the way I really love the design of UFFI , very clean and quite easy to understand , great work to you and Igor :) On Tue, Nov 8, 2016 at 1:54 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > On 8 Nov 2016, at 12:49, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > I was reaching a similar conclusion > > Currently I have a void pointer to the struct with the members I mentioned > > I can get char[100] > > pointerToStruct fromCString > > and I can get the int with > > pointerToStruct getHandle integerAt: 101 size:4 signed: false > > so if I want to pass the address of the pointer to my YourStruct instance > will I have to initialize with > > YourStruct fromHandler: (pointerToStruct getHandle) > > is this a correct and safe way to pass the address ? > > > yes. > > Esteban > > > > On Tue, Nov 8, 2016 at 1:21 PM Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > it never could. > you need to do a âspecial typeâ, who has to be something like: > > YourStruct class>>initialize > Char100 := FFITypeArray ofType: #char. > > fieldsDesc > ^ #( > Char100 data; > int count; > ) > > but thenâ¦ you want to optimise that and in field accessors, who will look > something like this: > > YourStruct >>data > "This method was automatically generated" > ^(FFITypeArray ofType: #char size: 100) fromHandle: (handle > copyFrom: 1 to: 100) > > you can change that for: > > YourStruct >>data > "This method was automatically generated" > ^Char100 fromHandle: (handle copyFrom: 1 to: 100) > > and same for setter. > (other way will work, but it will be suboptimal) > > Esteban > > > On 8 Nov 2016, at 12:10, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > > > I have FFIExternalStructure which has at class side > > > > fieldsDesc > > ^#( > > char data[100]; > > int count; > > ) > > > > if I try to do > > > > EphCPPTestStructure rebuildFieldAccessors . > > > > in order to generate the accessors for the members of the struct it > complains with an error that it does not recognise the type of " [ " > > > > Does that mean that char arrays are other arrays are not supported as > struct members or will I have to do this manually ? > > >

Nov. 8, 2016

Re: [Pharo-users] UFFI can not generate Structure accessor of type char[100]

by Esteban Lorenzano

> On 8 Nov 2016, at 12:49, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > I was reaching a similar conclusion > > Currently I have a void pointer to the struct with the members I mentioned > > I can get char[100] > > pointerToStruct fromCString > > and I can get the int with > > pointerToStruct getHandle integerAt: 101 size:4 signed: false > > so if I want to pass the address of the pointer to my YourStruct instance will I have to initialize with > > YourStruct fromHandler: (pointerToStruct getHandle) > > is this a correct and safe way to pass the address ? yes. Esteban > > > On Tue, Nov 8, 2016 at 1:21 PM Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > it never could. > you need to do a âspecial typeâ, who has to be something like: > > YourStruct class>>initialize > Char100 := FFITypeArray ofType: #char. > > fieldsDesc > ^ #( > Char100 data; > int count; > ) > > but thenâ¦ you want to optimise that and in field accessors, who will look something like this: > > YourStruct >>data > "This method was automatically generated" > ^(FFITypeArray ofType: #char size: 100) fromHandle: (handle copyFrom: 1 to: 100) > > you can change that for: > > YourStruct >>data > "This method was automatically generated" > ^Char100 fromHandle: (handle copyFrom: 1 to: 100) > > and same for setter. > (other way will work, but it will be suboptimal) > > Esteban > > > On 8 Nov 2016, at 12:10, Dimitris Chloupis <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > > > > I have FFIExternalStructure which has at class side > > > > fieldsDesc > > ^#( > > char data[100]; > > int count; > > ) > > > > if I try to do > > > > EphCPPTestStructure rebuildFieldAccessors . > > > > in order to generate the accessors for the members of the struct it complains with an error that it does not recognise the type of " [ " > > > > Does that mean that char arrays are other arrays are not supported as struct members or will I have to do this manually ? > >

Nov. 8, 2016

Re: [Pharo-users] UFFI can not generate Structure accessor of type char[100]

by Dimitris Chloupis

I was reaching a similar conclusion Currently I have a void pointer to the struct with the members I mentioned I can get char[100] pointerToStruct fromCString and I can get the int with pointerToStruct getHandle integerAt: 101 size:4 signed: false so if I want to pass the address of the pointer to my YourStruct instance will I have to initialize with YourStruct fromHandler: (pointerToStruct getHandle) is this a correct and safe way to pass the address ? On Tue, Nov 8, 2016 at 1:21 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > it never could. > you need to do a âspecial typeâ, who has to be something like: > > YourStruct class>>initialize > Char100 := FFITypeArray ofType: #char. > > fieldsDesc > ^ #( > Char100 data; > int count; > ) > > but thenâ¦ you want to optimise that and in field accessors, who will look > something like this: > > YourStruct >>data > "This method was automatically generated" > ^(FFITypeArray ofType: #char size: 100) fromHandle: (handle > copyFrom: 1 to: 100) > > you can change that for: > > YourStruct >>data > "This method was automatically generated" > ^Char100 fromHandle: (handle copyFrom: 1 to: 100) > > and same for setter. > (other way will work, but it will be suboptimal) > > Esteban > > > On 8 Nov 2016, at 12:10, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > > > I have FFIExternalStructure which has at class side > > > > fieldsDesc > > ^#( > > char data[100]; > > int count; > > ) > > > > if I try to do > > > > EphCPPTestStructure rebuildFieldAccessors . > > > > in order to generate the accessors for the members of the struct it > complains with an error that it does not recognise the type of " [ " > > > > Does that mean that char arrays are other arrays are not supported as > struct members or will I have to do this manually ? > > >

Nov. 8, 2016

Re: [Pharo-users] UFFI can not generate Structure accessor of type char[100]

by Esteban Lorenzano

it never could. you need to do a âspecial typeâ, who has to be something like: YourStruct class>>initialize Char100 := FFITypeArray ofType: #char. fieldsDesc ^ #( Char100 data; int count; ) but thenâ¦ you want to optimise that and in field accessors, who will look something like this: YourStruct >>data "This method was automatically generated" ^(FFITypeArray ofType: #char size: 100) fromHandle: (handle copyFrom: 1 to: 100) you can change that for: YourStruct >>data "This method was automatically generated" ^Char100 fromHandle: (handle copyFrom: 1 to: 100) and same for setter. (other way will work, but it will be suboptimal) Esteban > On 8 Nov 2016, at 12:10, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > I have FFIExternalStructure which has at class side > > fieldsDesc > ^#( > char data[100]; > int count; > ) > > if I try to do > > EphCPPTestStructure rebuildFieldAccessors . > > in order to generate the accessors for the members of the struct it complains with an error that it does not recognise the type of " [ " > > Does that mean that char arrays are other arrays are not supported as struct members or will I have to do this manually ?

Nov. 8, 2016

UFFI can not generate Structure accessor of type char[100]

by Dimitris Chloupis

I have FFIExternalStructure which has at class side fieldsDesc ^#( char data[100]; int count; ) if I try to do EphCPPTestStructure rebuildFieldAccessors . in order to generate the accessors for the members of the struct it complains with an error that it does not recognise the type of " [ " Does that mean that char arrays are other arrays are not supported as struct members or will I have to do this manually ?

Nov. 8, 2016

Re: [Pharo-users] about balkanisation

by Thierry Goubier

Hi Dale, 2016-11-08 2:03 GMT+01:00 Dale Henrichs <dale.henrichs(a)gemtalksystems.com>: > [ snip ... ] > > yes I think this is the area where a Metallo Project Browser comes into > play. The technology for committing the dirty packages in a a > ConfigurationOf has been around for quite awhile, but a tool that unifies > the "multi-package" commit for ConfigurationOf and BaselineOf hasn't popped > out of the wood work ... > I'm having some issues with the scripting approach of Metacello, for that. Just manipulating a baseline in the Metacello registry (locking it) seems to be like writing a compiler code generation item: write a Metacello script ;) (Metacello>>#lock contains interesting code). > > > What is a bit annoying, really, is this talk of rewriting everything where > some of the pieces (the project browsing you're talkin about, for example) > is already there in the image, just not exposed. > > Well I am annoyed as well .. I would say that perhaps we are in screaming > agreement ... I've said that I don't think it's a lot of work to do the > project-centric tool. but a project-centric tool that encompasses both > ConfigurationOf and BaselineOf will expose the features that "are already > there" > > > I'm trying to code a little something for that... stay tuned for a > screenshot soon. > > Cool:) > And here it is! I'm still fighting with the Metacello lock / unlock thing. [image: Images intÃ©grÃ©es 1] If Pharo was more really modular in configurations and baselines, then I would see more things into the registry and I could group packages based on that (instead of having to prepare a ad-hoc classification for my my browser). Thierry > Dale >

Nov. 8, 2016

Linking issues to versions (bug analysis) in pharo

by Yuriy Tymchuk

Hi, has anybody done anything with bug analysis in Pharo? I know that the most common approach is to see in which version an issue was closed and what code was changed and when was that code introduced and as the result you have lifespans of bugs. Other suggestions are also welcome :) Uko

Nov. 8, 2016

Re: [Pharo-users] [ALERT] Pharo by Example version 5 is about to be released

by Ben Coman

On Tue, Nov 8, 2016 at 4:17 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > Another pulll request > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/180 > But I messed this one up. It contains the commits from the other pull > request. If PR179 is merged first, it shouldn't matter (IIUC). cheers -ben > I can fix this (later) or maybe it can just be merged (can I remove a commit > from a branch with githubs web-interface(!) ? > > > 2016-11-08 1:00 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >> >> >> >> 2016-11-07 8:47 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>> >>> Am 06.11.2016 21:04 schrieb "Dimitris Chloupis" <kilon.alios(a)gmail.com>: >>> > >>> > yeah as I said the chapter needs a complete rewrite. I am not even it >>> > is necessary to exist separately. >>> > >>> > On Sun, Nov 6, 2016 at 9:27 PM Nicolai Hess <nicolaihess(a)gmail.com> >>> > wrote: >>> >> >>> >> 2016-11-03 15:11 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>> >>> >>> >>> >>> >>> >>> >>> 2016-11-03 15:02 GMT+01:00 stepharo <stepharo(a)free.fr>: >>> >>>> >>> >>>> Hi nicolai >>> >>>> >>> >>>> I started to work on the reflection chapter. >>> >>> >>> >>> >>> >>> >>> >>> The reflection chapter (and maybe some other too) could new some new >>> >>> screenshots. >>> >> >>> >> >>> >> Actually, the reflection chapter needs some more rewrites (not only >>> >> updated screenshots). Some examples just aren't >>> >> applicable anymore because we don't have refactoring browser >>> >> preinstalled and although Nautilus can do alot, its missing >>> >> the full set of menus for creating scoped environments. >>> >> I'll try to rewrite those parts. >> >> pull request for this c hapter: >> >> https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/179 >> >> In short: >> updated screenshots >> replace some more "explore/explorer" by inspect/inspector >> rewrote the RefactoringBrowser parts, use RBBrowserEnvironment insteand of >> BrowserEnvironment >> fix some differences in LoggingProxy (something had changed in >> ProtoObject/Object implementation), some methods like #rect: are renamed in >> the actual Pharo 5.0 image. >> #haltIf: was broken, as the example with add: / testAdd: traps into an >> infinite loop because we now call add: everytime we lookup the add: sender >> I replaced this with an example that uses Morph>>#openInWorld instead of >> OrderedCollection>>#add: >> Replaced MethodContext by Context as the name changed in Pharo 5. Added a >> description why we call the inspector on thisContext a "poor mans debugger" >> :-) >> fix some changed SystemNavigation methods. >> Some code examples show the in image method version that had changed >> (other names or otherwise refactored). >> >> so far. But I'll do another pass >> >>> >>> >> >>> >>>> >>> >>>> Now hacking PharoDoc :) >>> >>>> >>> >>>> Stef >>> >>>> >>> >>>> >>> >>>> Le 3/11/16 Ã 14:29, Nicolai Hess a Ã©crit : >>> >>>>> >>> >>>>> >>> >>>>> >>> >>>>> 2016-10-27 13:32 GMT+02:00 Dimitris Chloupis >>> >>>>> <kilon.alios(a)gmail.com>: >>> >>>>>> >>> >>>>>> In case someone missed it I will be doing a release for version 5 >>> >>>>>> (pharo version = pbe version) this weekend , since we had Pharo 7 initiated >>> >>>>>> few days ago. >>> >>>>>> >>> >>>>>> Essentially that means that the repo will be tagged for version 5, >>> >>>>>> which means a git commit is associated as a last commit for that version and >>> >>>>>> there will be a frozen release - download for Pharo by Example version 5. >>> >>>>>> After that we move to Pharo By Example version 6 or PBE6 for short >>> >>>>>> >>> >>>>>> The repo wont change otherwise and the process of submitting >>> >>>>>> commits, pull requests and issues remains the same. >>> >>>>>> >>> >>>>>> If you have found a flaw of any sort in the documentation , please >>> >>>>>> open an issue in the github issue tracker that can be found here >>> >>>>>> >>> >>>>>> >>> >>>>>> https://github.com/SquareBracketAssociates/UpdatedPharoByExample/issues >>> >>>>>> >>> >>>>>> I will try to fix any problem reported but if I cannot , the fix >>> >>>>>> will have to move to version 6 >>> >>>>>> >>> >>>>>> As always thanks to all people contributing into the impossible >>> >>>>>> .... making Pharo more amazing >>> >>>>>> >>> >>>>>> If you want to contribute feel free to do so with a pull request. >>> >>>>>> >>> >>>>>> Does not matter if you are beginner because even minor corrections >>> >>>>>> like correcting mistakes in the grammar or content of the text, updated >>> >>>>>> pictures, or just a few lines of extra info are more than enough and more >>> >>>>>> than welcomed. Many Pharo beginners have already done so . >>> >>>>>> >>> >>>>>> -Salute to fellow Guardians of The Light >>> >>>>> >>> >>>>> >>> >>>>> I found some problems, but I don't have time to report/fix them >>> >>>>> now, I 'll try to report them >>> >>>>> later (today or tomorrow). >>> >>>>> >>> >>>>> >>> >>>> >>> >>> >>> >>> I know fixed most text in the chapter. At least there are no notes on >>> tools that aren't there anymore and I cut those things that aren't true >>> anyone. >>> But I would like to do some more pass over it. >>> Instead of just cutting, we could add some new things. >>> Explaing the RB-Pattern syntax is maybe to much. But I would like to add >>> it. >>> Maybe I'll put some notes on criticbrower and QA. >> >> >

Nov. 8, 2016