November 2021 - Pharo-users

[ANN] reprex-it

by HernÃ¡n Morales Durand

Hi all, I released reprex-it, an evaluator of Pharo code to formatted expressions, useful for sharing evaluated scripts on Github or Discord for example, or Microdown/Pillar books. Check the usage demo at the repository at https://github.com/hernanmd/reprex-it Please let me know what you think, what's missing, ideas or any comments. Also don't hesitate to open issues [1] if you experience some trouble. Enjoy! HernÃ¡n

Nov. 30, 2021

Re: [ANN] DataFrame Inspector

by HernÃ¡n Morales Durand

Hi Guille, El lun, 29 nov 2021 a las 9:49, Guillermo Polito (<guillermopolito(a)gmail.com>) escribiÃ³: > Ahhh super nice!! thanks for sharing :) > > Is it by default in polymath? > Good idea :) I opened an issue https://github.com/PolyMathOrg/PolyMath/issues/225 > > How do you decide what to plot in the inspector pane? Or you by default > always use histograms on every numerical column? > > Exactly, only numeric columns get histograms. HernÃ¡n > G > > El 27 nov 2021, a las 17:23, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> escribiÃ³: > > Hi everyone, > > I am glad to announce the first release of Data Inspector, a Pharo > inspector extension to operate and view DataFrame multiple information in a > same inspector view > > https://github.com/pharo-ai/data-inspector > > You may find installation instructions, features list, and example usage > demo in the GitHub documentation README. > > Please let us know what you think, what's missing, ideas or any comments. > Also don't hesitate to open issues [1] if you experience some trouble. > > Cheers! > > HernÃ¡n > > [1] https://github.com/pharo-ai/data-inspector/issues > > >

Nov. 29, 2021

Re: uFFI provide buffer to C

by Gerry Weaver

Hi Guillermo, Ah ok. I didnât realize that I could only have a single statement. I got it working now. Thanks to you and everyone that helped me out. Thanks, Gerry Gerry Weaver (800) 318-6118 From: Guillermo Polito <guillermopolito(a)gmail.com> Sent: Monday, November 29, 2021 3:11 AM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Re: uFFI provide buffer to C Hi Gerry, I think the point of Tomaz is that an FFI method can only have a single #ffiCall: statement. In your example, what you can do is to split your method in two methods: First a method with the mapping (following the idea of Tomaz but using libc) FFITutorial>>getHostNameInto: hostName ofLenght: length ^self ffiCall: #( int gethostname(char *hostName, int length) ) library: 'libc.so.6'. And then have a second method that calls this one: FFITutorial>>getHostName | nameBuffer | nameBuffer := ByteArray new: 256. self getHostNameInto: nameBuffer ofLenght: 256. ^nameBuffer asString Notice that converting the byte array buffer to string will only work by chance if the called function returns characters encoded in ascii. In Pharo strings are Unicode characters where each character is a unicode code-point. The best thing is to read the documentation of the library and check the encoding of the string that is put in the buffer to decode it accordingly, for example from utf8. G El 29 nov 2021, a las 0:56, Gerry Weaver <gerryw(a)compvia.com<mailto:gerryw@compvia.com>> escribiÃ³: Hi, Thanks for the example. Unfortunately, it doesn't work on Linux. Thanks, Gerry ________________________________ From: TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si<mailto:tomaz.turk@ef.uni-lj.si>> Sent: Sunday, November 28, 2021 11:39 AM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org>> Subject: [Pharo-users] Re: uFFI provide buffer to C Hi, try with this: FFITutorial>>getHostNameInto: hostName ofLenght: length ^self ffiCall: #( int gethostname(char *hostName, int length) ) library: 'Ws2_32.dll'. "... on Windows" >From Playground, you can then do: | name len | len := 50. name:= ByteArray new: len. FFITutorial new getHostNameInto: name ofLenght: len. name inspect. I hope this helps. Best wishes, Tomaz

Nov. 29, 2021

Platform studies

by Rafael Luque

Hi all. I'm enjoying reading some books of the Platform Studies series by the MIT Press (https://mitpress.mit.edu/books/series/platform-studies) Specifically, I'm reading "The future was here" about the Amiga and "Racing the Beam" about the Atari VCS. What I like about these books is how they try to study the relationships between the hardware and software design of these computing platforms and the creative works produced on these systems. The books study these media from the technical point of view, but also deep into their social and cultural aspects. I'd like this kind of critical study about the Smalltalk platform. Do you know about any book or research in this style? Thank you. ~ Rafael Luque

Nov. 29, 2021

Re: uFFI provide buffer to C

by Sven Van Caekenberghe

> On 29 Nov 2021, at 10:10, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi Gerry, > > I think the point of Tomaz is that an FFI method can only have a single #ffiCall: statement. > In your example, what you can do is to split your method in two methods: > > First a method with the mapping (following the idea of Tomaz but using libc) > > FFITutorial>>getHostNameInto: hostName ofLenght: length >> ^self ffiCall: #( int gethostname(char *hostName, int length) ) library: 'libc.so.6'. > > And then have a second method that calls this one: > > FFITutorial>>getHostName > > | nameBuffer | > > nameBuffer := ByteArray new: 256. > > self getHostNameInto: nameBuffer ofLenght: 256. > > ^nameBuffer asString > > Notice that converting the byte array buffer to string will only work by chance if the called function returns characters encoded in ascii. > In Pharo strings are Unicode characters where each character is a unicode code-point. In general #utf8Decoded is better than #asString since UTF-8 includes 7-bit ASCII. It will fail when the native encoding is one of the simpler byte encodings, like Latin1 (or iso-8859-1), though. > The best thing is to read the documentation of the library and check the encoding of the string that is put in the buffer to decode it accordingly, for example from utf8. > > G > > >> El 29 nov 2021, a las 0:56, Gerry Weaver <gerryw(a)compvia.com> escribiÃ³: >> >> Hi, >> >> Thanks for the example. Unfortunately, it doesn't work on Linux. >> >> Thanks, >> Gerry >> >> >> From: TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> >> Sent: Sunday, November 28, 2021 11:39 AM >> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> Subject: [Pharo-users] Re: uFFI provide buffer to C >> >> Hi, >> >> try with this: >> >> FFITutorial>>getHostNameInto: hostName ofLenght: length >> ^self ffiCall: #( int gethostname(char *hostName, int length) ) library: 'Ws2_32.dll'. "... on Windows" >> >> From Playground, you can then do: >> >> | name len | >> len := 50. >> name:= ByteArray new: len. >> FFITutorial new getHostNameInto: name ofLenght: len. >> name inspect. >> >> I hope this helps. >> >> Best wishes, >> Tomaz >

Nov. 29, 2021

Re: uFFI provide buffer to C

by Guillermo Polito

Hi Gerry, I think the point of Tomaz is that an FFI method can only have a single #ffiCall: statement. In your example, what you can do is to split your method in two methods: First a method with the mapping (following the idea of Tomaz but using libc) FFITutorial>>getHostNameInto: hostName ofLenght: length > ^self ffiCall: #( int gethostname(char *hostName, int length) ) library: 'libc.so.6'. And then have a second method that calls this one: FFITutorial>>getHostName | nameBuffer | nameBuffer := ByteArray new: 256. self getHostNameInto: nameBuffer ofLenght: 256. ^nameBuffer asString Notice that converting the byte array buffer to string will only work by chance if the called function returns characters encoded in ascii. In Pharo strings are Unicode characters where each character is a unicode code-point. The best thing is to read the documentation of the library and check the encoding of the string that is put in the buffer to decode it accordingly, for example from utf8. G > El 29 nov 2021, a las 0:56, Gerry Weaver <gerryw(a)compvia.com> escribiÃ³: > > Hi, > > Thanks for the example. Unfortunately, it doesn't work on Linux. > > Thanks, > Gerry > > > From: TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> > Sent: Sunday, November 28, 2021 11:39 AM > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] Re: uFFI provide buffer to C > > Hi, > > try with this: > > FFITutorial>>getHostNameInto: hostName ofLenght: length > ^self ffiCall: #( int gethostname(char *hostName, int length) ) library: 'Ws2_32.dll'. "... on Windows" > > From Playground, you can then do: > > | name len | > len := 50. > name:= ByteArray new: len. > FFITutorial new getHostNameInto: name ofLenght: len. > name inspect. > > I hope this helps. > > Best wishes, > Tomaz

Nov. 29, 2021

Re: [ANN] DataFrame Inspector

by Guillermo Polito

Ahhh super nice!! thanks for sharing :) Is it by default in polymath? How do you decide what to plot in the inspector pane? Or you by default always use histograms on every numerical column? G > El 27 nov 2021, a las 17:23, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> escribiÃ³: > > Hi everyone, > > I am glad to announce the first release of Data Inspector, a Pharo inspector extension to operate and view DataFrame multiple information in a same inspector view > > https://github.com/pharo-ai/data-inspector <https://github.com/pharo-ai/data-inspector> > > You may find installation instructions, features list, and example usage demo in the GitHub documentation README. > > Please let us know what you think, what's missing, ideas or any comments. Also don't hesitate to open issues [1] if you experience some trouble. > > Cheers! > > HernÃ¡n > > [1] https://github.com/pharo-ai/data-inspector/issues <https://github.com/pharo-ai/data-inspector/issues>

Nov. 29, 2021

Re: uFFI provide buffer to C

by Gerry Weaver

Hi, Thanks for the example. Unfortunately, it doesn't work on Linux. Thanks, Gerry ________________________________ From: TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> Sent: Sunday, November 28, 2021 11:39 AM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Re: uFFI provide buffer to C Hi, try with this: FFITutorial>>getHostNameInto: hostName ofLenght: length ^self ffiCall: #( int gethostname(char *hostName, int length) ) library: 'Ws2_32.dll'. "... on Windows" >From Playground, you can then do: | name len | len := 50. name:= ByteArray new: len. FFITutorial new getHostNameInto: name ofLenght: len. name inspect. I hope this helps. Best wishes, Tomaz

Nov. 28, 2021

Re: uFFI provide buffer to C

by TomaÅ¾ Turk

Hi, try with this: FFITutorial>>getHostNameInto: hostName ofLenght: length ^self ffiCall: #( int gethostname(char *hostName, int length) ) library: 'Ws2_32.dll'. "... on Windows" >From Playground, you can then do: | name len | len := 50. name:= ByteArray new: len. FFITutorial new getHostNameInto: name ofLenght: len. name inspect. I hope this helps. Best wishes, Tomaz

Nov. 28, 2021

Re: uFFI provide buffer to C

by Gerry Weaver

Hi, I'm just trying to work out how to do it. Please find my latest attempt below. The docs aren't much help with this. FFITutorial>>getHostName | nameBuffer | nameBuffer := ByteArray new: 256. self ffiCall: #( int gethostname(ByteArray *nameBuffer, int 256) ) library: 'libc.so.6'. ^nameBuffer asString Thanks, Gerry ________________________________ From: Esteban Lorenzano <estebanlm(a)netc.eu> Sent: Sunday, November 28, 2021 3:09 AM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Cc: pharo-users(a)lists.pharo.org <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Re: uFFI provide buffer to C hi, it should be ByteArray. if you explain more in detail your problem, I can try to help you better :) Esteban On Nov 28 2021, at 9:20 am, Gerry Weaver <gerryw(a)compvia.com> wrote: Hello All, Pharo newbie here. I'm playing around with uFFI and I'm having trouble figuring out how to provide a buffer to C. It looks like maybe ByteArray would be the type, but it's not working. Would some one be so kind as to show me an example with the C function gethostname? Thanks, Gerry

Nov. 28, 2021