- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] eventual crashes pharo vm

by henry

Re-adding the list in case others were interested. - HH > -------- Original Message -------- > Subject: Re: [Pharo-dev] eventual crashes pharo vm > Local Time: August 13, 2017 3:59 PM > UTC Time: August 13, 2017 7:59 PM > From: henry(a)callistohouse.club > To: Stephane Ducasse <stepharo.self(a)gmail.com> > > Stef, please see version 4 and the test in RefIdentityTest. > > - HH > >> -------- Original Message -------- >> Subject: Re: [Pharo-dev] eventual crashes pharo vm >> Local Time: August 13, 2017 3:09 PM >> UTC Time: August 13, 2017 7:09 PM >> From: stepharo.self(a)gmail.com >> To: henry <henry(a)callistohouse.club> >> >> Does he do it systematically? >> I was checking if they extend blockcontext or others. >> Because it would be really nice. >> >> Stef >> >> On Sun, Aug 13, 2017 at 9:06 PM, henry <henry(a)callistohouse.club> wrote: >>> Sorry, loading works fine. It segfaults on Ubuntu 32-bit when I run the test >>> cases. >>> >>> - HH >>> >>> >>> -------- Original Message -------- >>> Subject: Re: [Pharo-dev] eventual crashes pharo vm >>> Local Time: August 13, 2017 2:58 PM >>> UTC Time: August 13, 2017 6:58 PM >>> From: stepharo.self(a)gmail.com >>> To: henry <henry(a)callistohouse.club>, Pharo Development List >>> <pharo-dev(a)lists.pharo.org> >>> >>> We have some instability with the VM. Now can you tell us more how it "blew >>> up"? >>> I browsed the code and nothing special jump to my eyes. >>> >>> Stef >>> >>> On Sun, Aug 13, 2017 at 2:08 PM, henry <henry(a)callistohouse.club> wrote: >>>> Hi all. I was testing with this eventual_test package and it blows up the >>>> pharo 6.1 vm. I"d welcome pointers >>>> >>>> http://www.squeaksource.com/TurquoiseTesting.html >>>> >>>> - HH >>>> >>>> >>> >>>

Aug. 13, 2017

Re: [Pharo-dev] Anybody using Orca Smalltalk to JavaScript?

by Stephan Eggermont

Frank wrote: > I feel sorry for you if you really have not yet understood that proper, early and complete documentation and comments ARE ONLY an investment in the code, because they save time and efforts later on, which always pay back - mostly multiple times. Perhaps you might want to explain to me the return on investment of the Orca documentation then? Zero users, zero return on investment. I feel annoyed if you talk in absolutes like that, because I know that there are lots of situations where creating documentation is a waste of effort. And I have also been bitten by lack of documentation. And I have even been in a situation where both happened at the same time, where a lot of effort was put in creating the wrong kind of documentation. Oh, and I even wrote a bit of documentation myself. I have been thought many things at university, and there were many more things I had to learn in industry. And from open source projects, which have other things to teach. Investing means making decisions. Fully documented non-working code has no value. Working code that no-one can use neither. Your current communication is manipulative: you try to put yourself in a dominant position by using absolutes, saying you feel sorry for me, and bragging about your experience. That annoys me. If you want to convince me, use arguments. Stephan https://en.m.wikipedia.org/wiki/Nonviolent_Communication

Aug. 13, 2017

Re: [Pharo-dev] PharoJS crashes at first try

by Frank-B

Stephane, thank you for your open words. 1) No I am NOT Frank Lesser and I will communicate this even clearer in a personal email to you. 2) I had tried to make very clear that I see the Pharo project very positive and my critics as being (at least intended) constructive. 3) I never care about my reputation. I only care about truth, facts and a sincere appearance. Few people appreciate this attitude and I do not value the others all too high or seriously. Unfortunately, we all have to live in these timees of universal lies, deception and fraud. You probably know the good German word "LÃ¼genpresse" and my version is: "the current Zeitgeist equals LÃ¼genpresse". 4) I have some good, solid and unusual ideas how I could improve the Pharo project considerably but for several reasons it is much to early to discuss this. It will take another 2-3 years and I will definitely come back when the time has come on my side. 5) As a contributor in the general Pharo sense I am currently neither capable (working 85-100 hours a week on my projects) nor eligible and the latter reason is not simple to explain, so I leave it at that for now. Frank -- View this message in context: http://forum.world.st/PharoJS-crashes-at-first-try-tp4960686p4960770.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 13, 2017

Re: [Pharo-dev] Github and Fogbugz integration

by Stephane Ducasse

Tx guille! On Sun, Aug 13, 2017 at 3:05 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi all, > > we just configured fogbugz and github integration as follows: > > http://help.fogcreek.com/8048/integration-with-git > > Quoting the instructions: > > > 1. Now you can refer to your FogBugz cases in your GitHub commits > (just add â*case <number>*â in the commit message) > > > That will link your fogbugz issues to the commits on integration. > > Sadly, this just works for the integration of commits into the main > branches, not pull requests. For pull request integration we will probably > need a home made solution. > > Cheers, > Guille et al > > -- > > > > 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> >

Aug. 13, 2017

Re: [Pharo-dev] [Vm-dev] vm crash when using rairedTo: with fractions

by Stephane Ducasse

Tx eliot. On Fri, Aug 11, 2017 at 12:55 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Andrei, > > On Thu, Aug 10, 2017 at 3:02 AM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: >> >> >> Hi, >> >> I was executing this code '(2009/2000) ** (3958333/100000)' with the >> Pharo6.1 distribution and the vm crashed with she stack attached below. >> Tried it on both mac and windows 10. >> Seems that #raisedTo: has a special case for fractions that ends up >> calling #nthRoot: like '2009 nthRoot: 100000' leading to the crash. > > > The plugin is now fixed; see VMMaker.oscog-eem.2262. I'll generate code > soon (am debugging something you're familiar with that takes several hours > to run and don't want to generate sources while it's running). But I'm glad > you've found a better way! This case creates 600k byte large integers and > takes forever to run :-) > >> >> Cheers, >> Andrei >> >> >> 0xaddeac M LargePositiveInteger(Integer)>quo: 0x314093e8: a(n) >> LargePositiveInteger >> 0xaddec8 M LargePositiveInteger(LargeInteger)>quo: 0x314093e8: a(n) >> LargePositiveInteger >> 0xaddee8 M LargePositiveInteger(Integer)>// 0x314093e8: a(n) >> LargePositiveInteger >> 0xaddf04 M LargePositiveInteger(LargeInteger)>// 0x314093e8: a(n) >> LargePositiveInteger >> 0xaddf34 I LargePositiveInteger(Integer)>nthRootTruncated: 0x30cc8350: >> a(n) LargePositiveInteger >> 0xaddf5c I LargePositiveInteger(Integer)>nthRootRounded: 0x30cc8350: a(n) >> LargePositiveInteger >> 0xaddf88 I SmallInteger(Integer)>nthRoot: 0xfb3=2009 >> 0xaddfb4 I Fraction>nthRoot: 0x4f9a940: a(n) Fraction >> 0xaddfd8 I Fraction(Number)>raisedTo: 0x4f9a940: a(n) Fraction >> 0xaddffc I Fraction(Number)>** 0x4f9a940: a(n) Fraction >> 0xade018 M UndefinedObject>DoIt 0x5fe5d00: a(n) UndefinedObject >> 0xade048 I OpalCompiler>evaluate 0x4f9a998: a(n) OpalCompiler >> 0xade074 I RubSmalltalkEditor>evaluate:andDo: 0x305e5878: a(n) >> RubSmalltalkEditor >> 0xade09c I RubSmalltalkEditor>highlightEvaluateAndDo: 0x305e5878: a(n) >> RubSmalltalkEditor >> 0xade0b8 M >> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>popupPrint >> 0x3062fdc8: a(n) GLMMorphicPharoScri >> enderer >> 0xade0d8 I MorphicAlarm(MessageSend)>value 0x4f9ab20: a(n) MorphicAlarm >> 0xade0f4 M MorphicAlarm>value: 0x4f9ab20: a(n) MorphicAlarm >> 0xade114 M WorldState>triggerAlarmsBefore: 0x71bb5e0: a(n) WorldState >> 0xade140 M WorldState>runLocalStepMethodsIn: 0x71bb5e0: a(n) WorldState >> 0xade164 M WorldState>runStepMethodsIn: 0x71bb5e0: a(n) WorldState >> 0xade180 M WorldMorph>runStepMethods 0x6ab7778: a(n) WorldMorph >> 0xade198 M WorldState>doOneCycleNowFor: 0x71bb5e0: a(n) WorldState >> 0xade1b4 M WorldState>doOneCycleFor: 0x71bb5e0: a(n) WorldState >> 0xade1d0 M WorldMorph>doOneCycle 0x6ab7778: a(n) WorldMorph >> 0xade1e8 M WorldMorph class>doOneCycle 0x6a9f960: a(n) WorldMorph class >> 0xade200 M [] in MorphicUIManager>spawnNewProcess 0x2cc88718: a(n) >> MorphicUIManager >> 0xade220 I [] in BlockClosure>newProcess 0x2f178150: a(n) BlockClosure >> > > > > -- > _,,,^..^,,,_ > best, Eliot

Aug. 13, 2017

Re: [Pharo-dev] Add JSONSchemas to NeoJSON

by henry

Thank you, Stef. I sent to him email, conditioned on his enjoying his vacations. - HH > -------- Original Message -------- > Subject: Re: [Pharo-dev] Add JSONSchemas to NeoJSON > Local Time: August 13, 2017 2:53 PM > UTC Time: August 13, 2017 6:53 PM > From: stepharo.self(a)gmail.com > To: henry <henry(a)callistohouse.club>, Pharo Development List <pharo-dev(a)lists.pharo.org> > > Hi henry > > Here is the email of sven Van Caekenberghe <sven(a)stfx.eu> > > He is probably on vacation else he would have replied. > This is great if you can extend neoJSON it is a nice and important > piece of software. > > Stef > > On Sat, Aug 12, 2017 at 10:04 PM, henry <henry(a)callistohouse.club> wrote: >> Is Sven still working on NeoJSON? I want to help expand it to use >> JSONSchemas. >> >> https://spacetelescope.github.io/understanding-json-schema/ >> >> I was looking at ASN1Module in Cryptography... >> >> - HH

Aug. 13, 2017

Re: [Pharo-dev] eventual crashes pharo vm

by Stephane Ducasse

We have some instability with the VM. Now can you tell us more how it "blew up"? I browsed the code and nothing special jump to my eyes. Stef On Sun, Aug 13, 2017 at 2:08 PM, henry <henry(a)callistohouse.club> wrote: > Hi all. I was testing with this eventual_test package and it blows up the > pharo 6.1 vm. I'd welcome pointers > > http://www.squeaksource.com/TurquoiseTesting.html > > - HH > >

Aug. 13, 2017

Re: [Pharo-dev] Add JSONSchemas to NeoJSON

by Tudor Girba

+1 Doru > On Aug 13, 2017, at 8:53 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi henry > > Here is the email of sven Van Caekenberghe <sven(a)stfx.eu> > > He is probably on vacation else he would have replied. > This is great if you can extend neoJSON it is a nice and important > piece of software. > > Stef > > On Sat, Aug 12, 2017 at 10:04 PM, henry <henry(a)callistohouse.club> wrote: >> Is Sven still working on NeoJSON? I want to help expand it to use >> JSONSchemas. >> >> https://spacetelescope.github.io/understanding-json-schema/ >> >> I was looking at ASN1Module in Cryptography... >> >> - HH > -- www.tudorgirba.com www.feenk.com âThe smaller and more pervasive the hardware becomes, the more physical the software gets."

Aug. 13, 2017

Re: [Pharo-dev] Add JSONSchemas to NeoJSON

by Stephane Ducasse

Hi henry Here is the email of sven Van Caekenberghe <sven(a)stfx.eu> He is probably on vacation else he would have replied. This is great if you can extend neoJSON it is a nice and important piece of software. Stef On Sat, Aug 12, 2017 at 10:04 PM, henry <henry(a)callistohouse.club> wrote: > Is Sven still working on NeoJSON? I want to help expand it to use > JSONSchemas. > > https://spacetelescope.github.io/understanding-json-schema/ > > I was looking at ASN1Module in Cryptography... > > - HH

Aug. 13, 2017

Re: [Pharo-dev] PharoJS crashes at first try

by Stephane Ducasse

Hi frank I think that you are slowly but steadily destroying your aura in this mailing-list, so be careful. I say that to help you. Filter are easy to set. We are all concerned that some of the solutions are not at the level where they should be. I'm sure that Noury like us all would love to have an engineer fully paid and working fully on PharoJS. Now you should consider that people in this community are - building nice libraries (just look at the Pharo success stories - we did not invent them) - sharing their code and valuing it - are concerned by documentation, speed, and robustness. You see take Zinc, NeoJSON, NeoCSV.... they are all HIGH quality, with nearly instant support from sven, with EXCELLENT documentation, FAST and continuously maintained. And for FREE. So of course not all the solutions in Pharo are like that. But we are trying. Now I do not know if you are the frank from lesser software I met in the past but if you do you may ask yourself what would be state of Pharo if you would have participated and shared. So far I never saw anything good or bad coming from this frank. And I was always asking myself if we would all work on closed code then a great system like Pharo would not exist. But we do share and we will continue to improve Pharo with or without you (remember U2 :)). Now if you want to join you are welcome. I can understand your frustration now the difference between you and me is that I decided not to be frustrated anymore and help building a better system. Stef Stef On Sun, Aug 13, 2017 at 8:35 PM, Frank-B <frank.berger.software(a)web.de> wrote: > Paul, > > >> What would you be willing to pay for a professionally commented, >> functioning, and documented PharoJS? > > Pardon, but don't you notice yourself how absurd this question is? > > If not - and I am afraid you don't, I tell you why: > - there is NOWHERE any proper listing of what this mysterious piece of > software does (the slides don't tell anything) > - before giving a quote, I would have to anylyse the architectural approach > - and compare it with alternatives - no info available (read the docs on > Orca and you know hwat I mean) > - and see who delivers under which conditions > - and how well things are documented. > > Be assured, that I am well prepared to pay accordingly for a proper product > that I can use, provided that I make the decition to delegate such essential > work to some outsider. > > This technical subject is a CORE feature of almost all of my future > products, plans, ideas etc and it is therefore vital to choose the best and > most fitting system. If there is no alternative, I would - in case of need - > develop it rather myself than depend on an (assumed for the moment) instable > and amateurish library. > > Frank > > > > > > -- > View this message in context: http://forum.world.st/PharoJS-crashes-at-first-try-tp4960686p4960738.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 13, 2017