- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] Pumping FFI documentation [WAS] FFI beginner question
by Ben Coman Sept. 25, 2019

Sept. 25, 2019

On Wed, 25 Sep 2019 at 13:51, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > Normally each time a PR is integrated in a book, the CI is generating the > PDF. > https://github.com/SquareBracketAssociates/Booklet-uFFI/releases > > So what you can do is to not bother and copy-edit and we fix the > corresponding pillar > if you break it. > Hey Stef :) I'm guessing you mean to encourage Ted to "not worry" rather than "not bother" https://www.phrasemix.com/phrases/not-bother-doing-something cheers -ben

2 1

FFI beginner question
by Richard O'Keefe Sept. 25, 2019

Sept. 25, 2019

I am developing a Smalltalk interface to an existing C library which I intend to make generally available. Naturally I am doing this in my own Smalltalk system first, where it's unsurprisingly easy for me. But when I have it working, I'd like to make a Pharo port available. I have never used the Foreign Function Interface in Pharo before and don't even know where to start. What should I read first? Is there a model project to imitate?

6 12

Difficulty to use Iceberg
by Brainstorms Sept. 24, 2019

Sept. 24, 2019

Jan Vrany <[hidden email]> wrote: > Hi, > > I'm experiencing difficulties (code loss, even) when trying to > commit code using Iceberg. > > I have a project with consist of some Pharo code and some > C++ code. Both parts kind of depend on each other. >... > Any suggestions? Would "git worktree add" solve your problem? This allows you to create multiple working trees that are all associated with the same repository. I expect it would allow Pharo to interact with the original working copy while providing a second working directory for your C++ co-development, but without the need to clone an additional working copy. -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

Reminder: Smalltalk Webcamp, 22nd of October
by Johan Brichau Sept. 24, 2019

Sept. 24, 2019

Hi, Are you doing Web development with Smalltalk? Then this meeting is for you. We organise an informal meetup on Smalltalk Web Technologies at the Yesplan offices. =============================================== Smalltalk WebCamp --------------------------- Date: Tuesday October 22nd, 2019 (9h30 -> 18h00) Location: Yesplan offices in Gent, Belgium. (www.yesplan.be <http://www.yesplan.be/>) =============================================== This is an un-conference: everyone is invited to actively participate by presenting their project. Come and share your web development experience with Smalltalk. Wether you are doing Seaside, Teapot, PharoJS, Amber, SqueakJs, Zinc REST, â¦ or anything else that involves Smalltalk and web technologies: come and share your experience! We provide ample time to discuss and collaborate on topics, meet people and have a beer in the evening. Attendance is free, but please register before October 15th if you are attending, so we can plan accordingly. Registration link: https://www.eventbrite.com/e/smalltalk-webcamp-tickets-69185265993 <https://www.eventbrite.com/e/smalltalk-webcamp-tickets-69185265993> At this time, there are 9 participants, excluding the Yesplan team. Questions? Please send me an email. Best regards Johan Brichau johan(a)yesplan.be <mailto:johan@yesplan.be>

4 3

Re: [Pharo-users] Code of Conduct
by Ben Coman Sept. 24, 2019

Sept. 24, 2019

makes me wonder whether he's such a machiavellian sociopath, or a useful idiot. On Thu, 19 Sep 2019 at 23:07, Eugen Leitl via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Let's see, I've posted one email to this list describing the dangers > of abusing CoCs I guess you refer to this one... > On Tue, 17 Sep 2019 at 19:39, Eugen Leitl via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > I agree. Technical people are too easy to exploit by malignant manipulators of people. > All too often they don't even realize it after the fact. Thats fairly benign and doubt it had anything to do with being blocked on github. > and one post to GitHub describing the motivations of > people who introduce CoCs, and immediately get banned on GitHub from > Note, the board member who blocked your GIthub account and deleted your post there also voiced their opinion as being... For me a "welcome and be nice" should be enough to just continue as before. I find the introduction of CoC was a noise we didn't need, our community was doing well and self-regulated without problem until now. So in spite of your implication, I doubt there is anything sinister from the CoC in play here. Comments such as "makes me wonder whether he's such a machiavellian sociopath, or a useful idiot." have been consistently condemned years before thought of a CoC. > I'm getting called a troll and a nobody in public by members of the > project, Its not that you are a "nobody", but actually you were "unknown to us" two days ago. Maybe you don't know Serge, but we've know him for years and his good work including governance of our GSoC participation so please consider why such comments from a newcomer may be dealt with as a troll. Community standards do not maintain themselves: They're maintained by people actively applying them, visibly, in public. Now personally I'm not going to condemn you on one slip. I've been told to pull my head in before and they were right - I was venting after a bad day at work. But no one held it against me long. These nontechnical and emotion-charge debates are infrequent and I hope get a chance to see how things normally run once we are past it. cheers -ben

16 44

Pharo 8 and Teapot
by sergio ruiz Sept. 24, 2019

Sept. 24, 2019

Just checking in on this. I started up a REST API project in Pharo 8. I thought I read somewhere that Teapot was failing tests in Pharo 8. I fired it up, and put together the beginnings of the project, and it looks fine. All tests pass. There was one SSL test that was not running in 7 either, but Iâll take a look at that when I get a chance. Thanks! ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV @sergio_101@mastodon.social https://sergio101.com http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

1 0

Where did all the Comments Go?
by Andrew Black Sept. 23, 2019

Sept. 23, 2019

My third attempt to post this ... 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

2 1

[ANN] Next Pharo Sprint: Sept 27
by Marcus Denker Sept. 23, 2019

Sept. 23, 2019

We will organize a Pharo sprint / Moose dojo Sept 27, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 Known Local Sprint meetings - Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come A list of all Pharo Event of the year an be found here: https://association.pharo.org/events

1 0

Re: [Pharo-users] Pharo-users Digest, Vol 77, Issue 67
by Vince Refiti Sept. 23, 2019

Sept. 23, 2019

Re: FFI beginner question The SQLite3 API is very well documented, and the UDBC-SQLite3 project ( https://github.com/astares/Pharo-UDBC) is a nice and clean binding to it. Look in UDBCSQLite3Library class. Vince On Mon, Sep 23, 2019 at 1:15 PM <pharo-users-request(a)lists.pharo.org> wrote: > Send Pharo-users mailing list submissions to > pharo-users(a)lists.pharo.org > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org > or, via email, send a message with subject or body 'help' to > pharo-users-request(a)lists.pharo.org > > You can reach the person managing the list at > pharo-users-owner(a)lists.pharo.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Pharo-users digest..." > > > Today's Topics: > > 1. FFI beginner question (Richard O'Keefe) > 2. Re: Code of Conduct (Richard O'Keefe) > 3. Re: FFI beginner question (Brainstorms) > 4. Re: Code of Conduct (Offray Vladimir Luna C?rdenas) > 5. Re: Code of Conduct (Steve Quezadas) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 23 Sep 2019 11:56:50 +1200 > From: "Richard O'Keefe" <raoknz(a)gmail.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] FFI beginner question > Message-ID: > <CABcYAd+DggCnoSaQr+D54Hc5= > Mb_ToRw8+o+saeEonipyMckzw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > I am developing a Smalltalk interface to an existing C library which I > intend to make generally available. Naturally I am doing this in my own > Smalltalk system first, where it's unsurprisingly easy for me. But when > I have it working, I'd like to make a Pharo port available. > > I have never used the Foreign Function Interface in Pharo before and > don't even know where to start. > > What should I read first? > Is there a model project to imitate? > > > > ------------------------------ > > Message: 2 > Date: Mon, 23 Sep 2019 12:40:46 +1200 > From: "Richard O'Keefe" <raoknz(a)gmail.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Code of Conduct > Message-ID: > < > CABcYAd+Xgn45++FKgDogZgEGzQfpPCg7+ZY4t+RaPxYSYLgctQ(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > This is not a question of left vs right. It's a question of > authoritarian vs libertarian. > And this is very relevant to the community. > It's also not a question of democracy vs central authority. > It's a question of vs ???????? vs goodspeak. > And this is very relevant to the community also. > > Pharo is "owned" by the people who do the bulk of the work on it, > and they are kind enough to share it with us. That there is such a > thing as a *Pharo* community is the result of their work. > > That there is such a thing as a Pharo *community* depends on the ability of > that community to communicate freely. This cuts BOTH ways. If people are > scared off by incivility, that's bad. If people are driven away by > incivility, > that's bad. But when you stop seeing rudeness as rudeness, which may be > amended, and start seeing it as crimethink, you drive people away, and that > is bad too. > > Let's consider a recent thread. I took the position that << and putOn: > were > confusing, unreliable, and unnecessary. The unreliability issue has been > addressed in Pharo 8; had I not been able to speak I would never have > learned > that. Some people apparently think that it improves readability, where I > find > that << impairs my ability to understand. The fact that BOTH sides were > able > to speak freely means that we now know (a) that there is no consensus for > removing them from the system and (b) if you want other people to read your > code you might want to think twice before using them, and we are all > better off. > But if criticising someone's opinion were construed as harassment, the > thread > would have been shut down before I displayed my code with a generalisation > that is worth having if << is worth having at all. > > I probably should have mentioned the Erlang code of conduct > http://erlang.org/download/erlang_org_code_of_conduct.txt > It is pretty a-political, has graduated response, and potential for > forgiveness. > > A code of conduct for *events* is another matter, which is why I bring > Erlang up. > http://erlang.org/pipermail/erlang-questions/2015-March/083849.html > is eye-opening. (It's mainly about Ruby community issues.) > > On Mon, 23 Sep 2019 at 11:51, Offray Vladimir Luna C?rdenas > <offray.luna(a)mutabit.com> wrote: > > > > My point was that this community, as a the big majority of FLOSS ones, > is not a democracy and *not* having a democracy has shown its benefits in > human endeavors like science, technology, hackerspaces and so on. > > > > I'll keep the rest of the conversation with you on the source code > repository and the PR. See you there. > > > > > > On 22/09/19 6:40 p. m., Steve Quezadas wrote: > > > > This isn't science, this is a community. We don't need a CoC, there > haven't been any problems on this list regarding nazis or whatever. This is > just a group of people trying to enforce their political ideologies on > everyone else. Let's just remove the CoC altogether and just replace it > with one line: "this maillist is about Pharo, anything else is offtopic". > > > > If you want to debate on the merits of Islam vs Christianity/ right vs > left / thugs vs racists , you are free to hold your opinion on some other > sub, but it's offtopic here. > > > > On Sun, Sep 22, 2019 at 4:23 PM Offray Vladimir Luna C?rdenas < > offray.luna(a)mutabit.com> wrote: > >> > >> There is no data to support such supposed majority. But even so, free, > libre, open source communities are not democracies. Imagine the quality of > code or argumentation based on perceived majorities? If science would be a > democracy, the earth would be "still" flat. > >> > >> On 22/09/19 6:04 p. m., Steve Quezadas wrote: > >> > >> I would say that the majority don't seem to be in favor of it. This > should be a democracy. > >> > >> On Sun, Sep 22, 2019 at 1:53 PM Offray Vladimir Luna C?rdenas < > offray.luna(a)mutabit.com> wrote: > >>> > >>> > >>> On 22/09/19 3:38 p. m., Steve Quezadas wrote: > >>> > > The discussion so far shows that CoC is not a distraction to many > >>> > > >>> > Actually, the discussion shows that the CoC is "a distraction to > many". > >>> > >>> Actually it shows that some people consider it a distraction, others > >>> don't. I think that every body here is able to form its own opinion on > >>> that and invest time and effort accordingly. > >>> > >>> Cheers, > >>> > >>> Offray > >>> > >>> > >>> > > > > ------------------------------ > > Message: 3 > Date: Sun, 22 Sep 2019 19:41:09 -0500 (CDT) > From: Brainstorms <wild.ideas(a)gmail.com> > To: pharo-users(a)lists.pharo.org > Subject: Re: [Pharo-users] FFI beginner question > Message-ID: <1569199269309-0.post(a)n4.nabble.com> > Content-Type: text/plain; charset=us-ascii > > I'm also interested in this... > > Any plans to draft a Pharo booklet on this subject? > > -Ted > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > > ------------------------------ > > Message: 4 > Date: Sun, 22 Sep 2019 21:37:19 -0500 > From: Offray Vladimir Luna C?rdenas <offray.luna(a)mutabit.com> > To: pharo-users(a)lists.pharo.org > Subject: Re: [Pharo-users] Code of Conduct > Message-ID: <ded9afcf-a557-9a0f-1aac-e45262b36d1a(a)mutabit.com> > Content-Type: text/plain; charset=utf-8 > > I agreed that the last decision should be on the ones who made the bulk > of the work. But I don't see relationship between a code of conduct and > not being able to talk about code or contributions quality. Just looking > at the FAQ of the original CoC that originated the whole think, I see a > lot of answers about the stuff being said on this thread (minorities, > left wing progressive agenda, diminish of code quality because of it, > mixing tech with non-tech stuff), so I will refer to it, because as I > said, I think that the PR should be the place for the bulk of the > discussion: > > https://www.contributor-covenant.org/faq > > The FAQ name goes pretty well, considering the amount of repeated > arguments they deal with. I think that many of the FAQ apply for other > CoCs, despite of the possible different nature of CoC for the online > community and the CoC for other face to face events. BTW, Thanks for the > links, both provide a better context for the emergence of the CoC in the > Erlang community. > > As said, I will try to see for specific contributions in the > correspondent PR in the repo, and made some if I have a one. For the > moment I'm trying to make my contributions on this thread, but is taking > a lot. > > Cheers, > > Offray > > On 22/09/19 7:40 p.?m., Richard O'Keefe wrote: > > This is not a question of left vs right. It's a question of > > authoritarian vs libertarian. > > And this is very relevant to the community. > > It's also not a question of democracy vs central authority. > > It's a question of vs ???????? vs goodspeak. > > And this is very relevant to the community also. > > > > Pharo is "owned" by the people who do the bulk of the work on it, > > and they are kind enough to share it with us. That there is such a > > thing as a *Pharo* community is the result of their work. > > > > That there is such a thing as a Pharo *community* depends on the ability > of > > that community to communicate freely. This cuts BOTH ways. If people > are > > scared off by incivility, that's bad. If people are driven away by > incivility, > > that's bad. But when you stop seeing rudeness as rudeness, which may be > > amended, and start seeing it as crimethink, you drive people away, and > that > > is bad too. > > > > Let's consider a recent thread. I took the position that << and putOn: > were > > confusing, unreliable, and unnecessary. The unreliability issue has been > > addressed in Pharo 8; had I not been able to speak I would never have > learned > > that. Some people apparently think that it improves readability, where > I find > > that << impairs my ability to understand. The fact that BOTH sides were > able > > to speak freely means that we now know (a) that there is no consensus for > > removing them from the system and (b) if you want other people to read > your > > code you might want to think twice before using them, and we are all > better off. > > But if criticising someone's opinion were construed as harassment, the > thread > > would have been shut down before I displayed my code with a > generalisation > > that is worth having if << is worth having at all. > > > > I probably should have mentioned the Erlang code of conduct > > http://erlang.org/download/erlang_org_code_of_conduct.txt > > It is pretty a-political, has graduated response, and potential for > forgiveness. > > > > A code of conduct for *events* is another matter, which is why I bring > > Erlang up. > > http://erlang.org/pipermail/erlang-questions/2015-March/083849.html > > is eye-opening. (It's mainly about Ruby community issues.) > > > > On Mon, 23 Sep 2019 at 11:51, Offray Vladimir Luna C?rdenas > > <offray.luna(a)mutabit.com> wrote: > >> My point was that this community, as a the big majority of FLOSS ones, > is not a democracy and *not* having a democracy has shown its benefits in > human endeavors like science, technology, hackerspaces and so on. > >> > >> I'll keep the rest of the conversation with you on the source code > repository and the PR. See you there. > >> > >> > >> On 22/09/19 6:40 p. m., Steve Quezadas wrote: > >> > >> This isn't science, this is a community. We don't need a CoC, there > haven't been any problems on this list regarding nazis or whatever. This is > just a group of people trying to enforce their political ideologies on > everyone else. Let's just remove the CoC altogether and just replace it > with one line: "this maillist is about Pharo, anything else is offtopic". > >> > >> If you want to debate on the merits of Islam vs Christianity/ right vs > left / thugs vs racists , you are free to hold your opinion on some other > sub, but it's offtopic here. > >> > >> On Sun, Sep 22, 2019 at 4:23 PM Offray Vladimir Luna C?rdenas < > offray.luna(a)mutabit.com> wrote: > >>> There is no data to support such supposed majority. But even so, free, > libre, open source communities are not democracies. Imagine the quality of > code or argumentation based on perceived majorities? If science would be a > democracy, the earth would be "still" flat. > >>> > >>> On 22/09/19 6:04 p. m., Steve Quezadas wrote: > >>> > >>> I would say that the majority don't seem to be in favor of it. This > should be a democracy. > >>> > >>> On Sun, Sep 22, 2019 at 1:53 PM Offray Vladimir Luna C?rdenas < > offray.luna(a)mutabit.com> wrote: > >>>> > >>>> On 22/09/19 3:38 p. m., Steve Quezadas wrote: > >>>>>> The discussion so far shows that CoC is not a distraction to many > >>>>> Actually, the discussion shows that the CoC is "a distraction to > many". > >>>> Actually it shows that some people consider it a distraction, others > >>>> don't. I think that every body here is able to form its own opinion on > >>>> that and invest time and effort accordingly. > >>>> > >>>> Cheers, > >>>> > >>>> Offray > >>>> > >>>> > >>>> > > > > > > > ------------------------------ > > Message: 5 > Date: Sun, 22 Sep 2019 20:14:26 -0700 > From: Steve Quezadas <steveeq1(a)gmail.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Code of Conduct > Message-ID: > <CAJzdPQV0YZXWePmfJ_PNbmBZeWq_Ov-St1iG9h8hd4dx=9CN= > w(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > > But the low rate at which marginalized people are recruited, and > > the high rate at which they leave the industry > <https://www.kaporcenter.org/tech-leavers/>, point to a larger > > cultural and systemic problem. > > Your interpreting this information with a SJW lens. Otherwise known as > "confirmation bias". Look at the low proportion of blacks and women who > apply for CS majors in college. Are you going to say that colleges are > using discriminatory practices to keep blacks and women from taking CS > classes? Maybe the bulk of the low recruitment statistics is simply due to > non-interest within that sub-culture. > > I believe this CoC is a way to wedge left-wing politics in a non-political > maillist. I want it out. > > On Sun, Sep 22, 2019 at 7:37 PM Offray Vladimir Luna C?rdenas < > offray.luna(a)mutabit.com> wrote: > > > I agreed that the last decision should be on the ones who made the bulk > > of the work. But I don't see relationship between a code of conduct and > > not being able to talk about code or contributions quality. Just looking > > at the FAQ of the original CoC that originated the whole think, I see a > > lot of answers about the stuff being said on this thread (minorities, > > left wing progressive agenda, diminish of code quality because of it, > > mixing tech with non-tech stuff), so I will refer to it, because as I > > said, I think that the PR should be the place for the bulk of the > > discussion: > > > > https://www.contributor-covenant.org/faq > > > > The FAQ name goes pretty well, considering the amount of repeated > > arguments they deal with. I think that many of the FAQ apply for other > > CoCs, despite of the possible different nature of CoC for the online > > community and the CoC for other face to face events. BTW, Thanks for the > > links, both provide a better context for the emergence of the CoC in the > > Erlang community. > > > > As said, I will try to see for specific contributions in the > > correspondent PR in the repo, and made some if I have a one. For the > > moment I'm trying to make my contributions on this thread, but is taking > > a lot. > > > > Cheers, > > > > Offray > > > > On 22/09/19 7:40 p. m., Richard O'Keefe wrote: > > > This is not a question of left vs right. It's a question of > > > authoritarian vs libertarian. > > > And this is very relevant to the community. > > > It's also not a question of democracy vs central authority. > > > It's a question of vs ???????? vs goodspeak. > > > And this is very relevant to the community also. > > > > > > Pharo is "owned" by the people who do the bulk of the work on it, > > > and they are kind enough to share it with us. That there is such a > > > thing as a *Pharo* community is the result of their work. > > > > > > That there is such a thing as a Pharo *community* depends on the > ability > > of > > > that community to communicate freely. This cuts BOTH ways. If people > > are > > > scared off by incivility, that's bad. If people are driven away by > > incivility, > > > that's bad. But when you stop seeing rudeness as rudeness, which may > be > > > amended, and start seeing it as crimethink, you drive people away, and > > that > > > is bad too. > > > > > > Let's consider a recent thread. I took the position that << and putOn: > > were > > > confusing, unreliable, and unnecessary. The unreliability issue has > been > > > addressed in Pharo 8; had I not been able to speak I would never have > > learned > > > that. Some people apparently think that it improves readability, where > > I find > > > that << impairs my ability to understand. The fact that BOTH sides > were > > able > > > to speak freely means that we now know (a) that there is no consensus > for > > > removing them from the system and (b) if you want other people to read > > your > > > code you might want to think twice before using them, and we are all > > better off. > > > But if criticising someone's opinion were construed as harassment, the > > thread > > > would have been shut down before I displayed my code with a > > generalisation > > > that is worth having if << is worth having at all. > > > > > > I probably should have mentioned the Erlang code of conduct > > > http://erlang.org/download/erlang_org_code_of_conduct.txt > > > It is pretty a-political, has graduated response, and potential for > > forgiveness. > > > > > > A code of conduct for *events* is another matter, which is why I bring > > > Erlang up. > > > http://erlang.org/pipermail/erlang-questions/2015-March/083849.html > > > is eye-opening. (It's mainly about Ruby community issues.) > > > > > > On Mon, 23 Sep 2019 at 11:51, Offray Vladimir Luna C?rdenas > > > <offray.luna(a)mutabit.com> wrote: > > >> My point was that this community, as a the big majority of FLOSS ones, > > is not a democracy and *not* having a democracy has shown its benefits in > > human endeavors like science, technology, hackerspaces and so on. > > >> > > >> I'll keep the rest of the conversation with you on the source code > > repository and the PR. See you there. > > >> > > >> > > >> On 22/09/19 6:40 p. m., Steve Quezadas wrote: > > >> > > >> This isn't science, this is a community. We don't need a CoC, there > > haven't been any problems on this list regarding nazis or whatever. This > is > > just a group of people trying to enforce their political ideologies on > > everyone else. Let's just remove the CoC altogether and just replace it > > with one line: "this maillist is about Pharo, anything else is offtopic". > > >> > > >> If you want to debate on the merits of Islam vs Christianity/ right vs > > left / thugs vs racists , you are free to hold your opinion on some other > > sub, but it's offtopic here. > > >> > > >> On Sun, Sep 22, 2019 at 4:23 PM Offray Vladimir Luna C?rdenas < > > offray.luna(a)mutabit.com> wrote: > > >>> There is no data to support such supposed majority. But even so, > free, > > libre, open source communities are not democracies. Imagine the quality > of > > code or argumentation based on perceived majorities? If science would be > a > > democracy, the earth would be "still" flat. > > >>> > > >>> On 22/09/19 6:04 p. m., Steve Quezadas wrote: > > >>> > > >>> I would say that the majority don't seem to be in favor of it. This > > should be a democracy. > > >>> > > >>> On Sun, Sep 22, 2019 at 1:53 PM Offray Vladimir Luna C?rdenas < > > offray.luna(a)mutabit.com> wrote: > > >>>> > > >>>> On 22/09/19 3:38 p. m., Steve Quezadas wrote: > > >>>>>> The discussion so far shows that CoC is not a distraction to many > > >>>>> Actually, the discussion shows that the CoC is "a distraction to > > many". > > >>>> Actually it shows that some people consider it a distraction, others > > >>>> don't. I think that every body here is able to form its own opinion > on > > >>>> that and invest time and effort accordingly. > > >>>> > > >>>> Cheers, > > >>>> > > >>>> Offray > > >>>> > > >>>> > > >>>> > > > > > > > > > >

2 1

Defensive programming or not
by Kasper Osterbye Sept. 23, 2019

Sept. 23, 2019

Cheers all, In trying to fix one of the issues in Pharo, I came to wonder about the prefered style in in dealing with preconditions to methods in Pharo. In the method Random>>nextInt: anInteger - There is a check if anInteger is negative - There is no check that anInteger is anInteger When should I put a guard there, and throw an early warning, and when is it part of the (often implicit pre-condition)? Best, Kasper

3 2