September 2019 - Pharo-users

Re: [Pharo-users] FFIExternalType hooks; naming convention

by TomaÅ¾ Turk

Hi, > Yes, but in general you do not need to implement your type, you can derive what you need from the ones existing. > Why you need to do it? I'm just curious, I'm sorry :-) Depending on the platform, there is a huge number of various types - just on Windows there are wchar_t, char16_t and char32_t implementations of "wide char", at least that I know of, and one asks himself when and whether to go all the way "down". > So readStrring is equivalent to fromCString, but I can imagine a better future where we have just one and it will > be readString :P :-) Thanks! Best wishes, Tomaz ------ Original Message ------ From: "Esteban Lorenzano" <estebanlm(a)gmail.com> To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> Sent: 21. 09. 2019 17:28:34 Subject: Re: [Pharo-users] FFIExternalType hooks; naming convention >HI, > >> On 21 Sep 2019, at 13:18, eftomi <tomaz.turk(a)ef.uni-lj.si> wrote: >> >> HI, >> >> I have a couple of questions regarding FFI: >> >> - If you want to create a new FFIExternalType subclass, which are the >> necessary hooks that should be implemented - like #externalType, >> #externalTypeSize â¦ on the class side and #basicHandle:at:, >> #basicHandle:at:put:, #stackValueParameterClass, etc. on the instance side? > >Yes, but in general you do not need to implement your type, you can derive what you need from the ones existing. >Why you need to do it? > >> >> - Is there anything else that should be done besides hooks - for instance >> another "entries" into FFIConstants class>>#initializeTypeConstants or even >> ExternalType>>#initializeAtomicTypes ? > >No. > >> >> - About naming standards: the ExternalData class has some methods that >> "grab" strings from the heap, like ExternalData>>#fromCString and >> ExternalData>>#readStringUTF8 - these two methods do the heavy work, however >> the method ExternalData>>#readString more or less just refers to >> ExternalData>>#fromCString. Is there any difference between "from..." and >> "readâ¦"? > >At the begining, there was fromCString. >Then someone else added readStringUTF8. >Then I added readString because I like coherence :) > >So readStrring is equivalent to fromCString, but I can imagine a better future where we have just one and it will be readString :P > >Esteban > >> >> Thanks! >> >> Best wishes, >> Tomaz >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > >

Sept. 21, 2019

Re: [Pharo-users] Code of Conduct

by Steve Quezadas

My issue is that this covenant is selectively applied to some things, but not others. The wording might change, but the cultural attitude will prevail on how it gets "enforced". Again, the best thing to do is simply keep it neutral and anything not related to pharo get thrown out as "off-topic". Harassment has never been a problem with this list. And any talk about the danger of "nazis" or "thugs" is irrelevent and should be thrown out. I, for one, don't want to see it on this list. On Sat, Sep 21, 2019 at 9:36 AM James Foster <Smalltalk(a)jgfoster.net> wrote: > A nice thing about open source and the use of Git is that changes can be > proposed and adopted quickly. Any proposal should be judged, not on whether > it is perfect, but whether it makes an improvement. As a corollary, donât > assume that the current state is the ideal, but treat it as a platform for > continuous improvements. > > In this case, the phrase you objected to was removed before you made your > comment. > > James > > > On Sep 20, 2019, at 11:43 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > > > > Le 19/09/2019 Ã 21:20, Esteban Lorenzano a Ã©crit : > >> > >> So we are going to take the simplest one we could find that still can > >> serve our community, you can see it here: > >> > >> https://github.com/pharo-project/pharo/pull/4660 > >> > > Hello, > > > > Given the heat up on the ml, I took a look on the PR. It looks honest > > and simple for but... > > > > ...I am really surprised -- worried will be more accurate ! -- by the > > second part of this sentence[1]. I think it is even dangerous! What is > > happening outside of the Pharo community should not be ruled by the > > 'WE'. The 'WE' is not the universal moral police or justice. If you > > think a bit about the Richard Stallman event, he was forced to withdraw > > of the Free Software Foundation because comments he made in a mailing > > list not related to FSF. He wrote his email contents were misinterpreted > > (and we know it happens often) and used against him. Whatever it is true > > or not, I don't see why you should be socially banned (or socially > > killed) from one place (or more like all place) because of what happen > > in another place. This kind of important decision can only be taken by > > the justice where all matter are taken in consideration. Imagine one of > > you kicked out of Pharo community because you loose your mind in another > > channel? It makes me feel a bit like the Aldous Huxley world. > > > > [1] /We will not tolerate harassment from anyone in the Pharo community, > > even outside of Pharoâs public communication channels./ > > > > Hilaire > > > > -- > > Dr. Geo > > http://drgeo.eu > > > > > > > > > > >

Sept. 21, 2019

Re: [Pharo-users] Code of Conduct

by James Foster

A nice thing about open source and the use of Git is that changes can be proposed and adopted quickly. Any proposal should be judged, not on whether it is perfect, but whether it makes an improvement. As a corollary, donât assume that the current state is the ideal, but treat it as a platform for continuous improvements. In this case, the phrase you objected to was removed before you made your comment. James > On Sep 20, 2019, at 11:43 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > > Le 19/09/2019 Ã 21:20, Esteban Lorenzano a Ã©crit : >> >> So we are going to take the simplest one we could find that still can >> serve our community, you can see it here: >> >> https://github.com/pharo-project/pharo/pull/4660 >> > Hello, > > Given the heat up on the ml, I took a look on the PR. It looks honest > and simple for but... > > ...I am really surprised -- worried will be more accurate ! -- by the > second part of this sentence[1]. I think it is even dangerous! What is > happening outside of the Pharo community should not be ruled by the > 'WE'. The 'WE' is not the universal moral police or justice. If you > think a bit about the Richard Stallman event, he was forced to withdraw > of the Free Software Foundation because comments he made in a mailing > list not related to FSF. He wrote his email contents were misinterpreted > (and we know it happens often) and used against him. Whatever it is true > or not, I don't see why you should be socially banned (or socially > killed) from one place (or more like all place) because of what happen > in another place. This kind of important decision can only be taken by > the justice where all matter are taken in consideration. Imagine one of > you kicked out of Pharo community because you loose your mind in another > channel? It makes me feel a bit like the Aldous Huxley world. > > [1] /We will not tolerate harassment from anyone in the Pharo community, > even outside of Pharoâs public communication channels./ > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > > >

Sept. 21, 2019

Re: [Pharo-users] FFIExternalType hooks; naming convention

by Esteban Lorenzano

HI, > On 21 Sep 2019, at 13:18, eftomi <tomaz.turk(a)ef.uni-lj.si> wrote: > > HI, > > I have a couple of questions regarding FFI: > > - If you want to create a new FFIExternalType subclass, which are the > necessary hooks that should be implemented - like #externalType, > #externalTypeSize â¦ on the class side and #basicHandle:at:, > #basicHandle:at:put:, #stackValueParameterClass, etc. on the instance side? Yes, but in general you do not need to implement your type, you can derive what you need from the ones existing. Why you need to do it? > > - Is there anything else that should be done besides hooks - for instance > another "entries" into FFIConstants class>>#initializeTypeConstants or even > ExternalType>>#initializeAtomicTypes ? No. > > - About naming standards: the ExternalData class has some methods that > "grab" strings from the heap, like ExternalData>>#fromCString and > ExternalData>>#readStringUTF8 - these two methods do the heavy work, however > the method ExternalData>>#readString more or less just refers to > ExternalData>>#fromCString. Is there any difference between "from..." and > "readâ¦"? At the begining, there was fromCString. Then someone else added readStringUTF8. Then I added readString because I like coherence :) So readStrring is equivalent to fromCString, but I can imagine a better future where we have just one and it will be readString :P Esteban > > Thanks! > > Best wishes, > Tomaz > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Sept. 21, 2019

Re: [Pharo-users] pharo for ios and android

by TomaÅ¾ Turk

I've found U8 for the android: http://alereimondo.no-ip.org/U8/313 . Best wishes TomaÅ¾ On Sat, 21 Sep 2019, 13:32 Stephan Eggermont, <stephan(a)stack.nl> wrote: > Steve Quezadas <steveeq1(a)gmail.com> wrote: > > I am going to the portland meetup this october and I noticed that one of > > the items listed is "Smalltalk on iOS and Android" which intrigues me. Is > > some Guilfoyle-type here writing a VM for these platforms? I was joking > > with a friend that we should write a vm for ios using the "smalltalk blue > > book" and it would be fun to learn how vm's work by trying to write > > sometihng for ios. Is someone already working on this? > > Craig Latta runs Smalltalk images on the javascript vm written by Bert > Freudenberg. Search for Caffeine > > Stephan > > > >

Sept. 21, 2019

Re: [Pharo-users] uFFI ExternalAddress challenges

by eftomi

Hi, as a wrap-up for this forum thread, I found an elegant way to take a result as C wchar_t* from an FFI call on Windows, based on the idea of ExternalData>>#fromCString. If anybody needs it: https://github.com/eftomi/pharo-uFFI-readWin32WideString. Best wishes, Tomaz -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 21, 2019

Re: [Pharo-users] pharo for ios and android

by Stephan Eggermont

Steve Quezadas <steveeq1(a)gmail.com> wrote: > I am going to the portland meetup this october and I noticed that one of > the items listed is "Smalltalk on iOS and Android" which intrigues me. Is > some Guilfoyle-type here writing a VM for these platforms? I was joking > with a friend that we should write a vm for ios using the "smalltalk blue > book" and it would be fun to learn how vm's work by trying to write > sometihng for ios. Is someone already working on this? Craig Latta runs Smalltalk images on the javascript vm written by Bert Freudenberg. Search for Caffeine Stephan

Sept. 21, 2019

FFIExternalType hooks; naming convention

by eftomi

HI, I have a couple of questions regarding FFI: - If you want to create a new FFIExternalType subclass, which are the necessary hooks that should be implemented - like #externalType, #externalTypeSize â¦ on the class side and #basicHandle:at:, #basicHandle:at:put:, #stackValueParameterClass, etc. on the instance side? - Is there anything else that should be done besides hooks - for instance another "entries" into FFIConstants class>>#initializeTypeConstants or even ExternalType>>#initializeAtomicTypes ? - About naming standards: the ExternalData class has some methods that "grab" strings from the heap, like ExternalData>>#fromCString and ExternalData>>#readStringUTF8 - these two methods do the heavy work, however the method ExternalData>>#readString more or less just refers to ExternalData>>#fromCString. Is there any difference between "from..." and "read..."? Thanks! Best wishes, Tomaz -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 21, 2019

Re: [Pharo-users] Code of Conduct

by Stephan Eggermont

Ramon Leon <ramon.leon(a)allresnet.com> wrote: > > It's not, identity politics are left wing politics That requires using a definition of left wing politics where neo-nazis and alt-right are left wing. That definition is not common here in Western Europe. Iâm happy for you and that you have enough privilege that you can afford to ignore politics. Stephan

Sept. 21, 2019

Re: [Pharo-users] Where did all the Comments Go?

by Sven Van Caekenberghe

Andrew, Are you saying all method and class comments are gone, in the whole system, or just the ones from new code that you loaded ? And is this the case only for you own code, or anything loaded extra ? Sven > On 20 Sep 2019, at 23:59, Andrew Black <apblack(a)pdx.edu> wrote: > > To try and make some progress, I copied a working image from another machine. On startup (on MacOS 10.14.6) I get this walkback: > > File class(ProtoObject)>>primitiveFailed: > File class(ProtoObject)>>primitiveFailed > File class>>fileDescriptorType: > File class>>fileDescriptorIsAvailable: > Stdio class>>standardIOStreamNamed:forWrite: > Stdio class>>stdout > VTermOutputDriver class>>stdout > BasicCommandLineHandler(CommandLineHandler)>>initializeStdout > BasicCommandLineHandler(CommandLineHandler)>>initialize > BasicCommandLineHandler>>initialize > BasicCommandLineHandler class(Behavior)>>new > [ self new activate ] in BasicCommandLineHandler class>>startUp: in Block: [ self new activate ] > BlockClosure>>cull: > WorkingSession>>executeDeferredStartupActions: > WorkingSession>>runStartup: > WorkingSession>>start: > SessionManager>>launchSnapshot:andQuit: > [ isImageStarting := self launchSnapshot: save andQuit: quit. > wait signal ] in SessionManager>>snapshot:andQuit: in Block: [ isImageStarting := self launchSnapshot: save and...etc... > [ self value. > Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... > > >> On 19 Sep 2019, at 17:43 , Andrew Black <apblack(a)pdx.edu> wrote: >> >> Iâm coming back to Pharo after not having used it for several months. Iâm pleased to see that Pharo 7 is now stable and that work has started on Pharo 8. >> >> I downloaded a new Pharo Launcher (the old one could no longer figure out which version of the VM to use), used the Launcher to create a Pharo 7.0 stable image, and started loading my packages into it from github. >> >> My attempt to install the baseline of my code failed when some initialization code could not get the definitionComment for my parser (which is written using SmaCC). Normally, SmaCC stores oneâs whole grammar _as a method comment_ in a method called definitionComment. Oddly, this method was empty, even though the version on disk (in the file Grace-Parser.package/GraceParser.class/class/definitionComment.st) contained the comment, as I expected. >> >> Hoping to at least complete the installation of my code, I manually copied the comment from this file into Calypso and saved the method. It looked fine, but as soon as I moved Calypso to another method, and then back again, the comment had disappeared. I experimented with adding comments to other methods: they looked fine, and I could save the method, but if I moved to another method and then back, the comment had disappeared. >> >> Class comments have also disappeared. >> >> I donât think that this is a Calypso problem, because the loading of code from git would not involve Calypso. Rather it is a code storage problem. I saw a File System primitive failure when I launched my new image, but ignored it; Iâm guessing that the comments disappear because they are only in the file system, whereas the code is in memory. And for some reason I canât access the sources file? The changes file ahs been created as expected. >> >> I just tried downloading the VM manually, and running the âstableâ image that I created, and this time got a different file system primitive failure on startup: #createDirectory in MacStore. >> >> Whatâs going on? Whatâs the right way to get a working Pharo in the New World Order? >> >> Andrew >> > > > > ____________________________ > Prof. Andrew P. Black > Department of Computer Science > Portland State University > Oregon, USA > > http://www.cs.pdx.edu/~black > Telephone: +1 503 725 2411 > > > >

Sept. 21, 2019