- Pharo-users - lists.pharo.org

How to run 32-bit image in 64-bit OS?
by HernÃ¡n Morales Durand Sept. 16, 2021

Sept. 16, 2021

Hello, Is there any guide on how to set up an environment for running 32-bit images in 64-bit OS? I have a bunch of 32-bit Pharo images (for example Pharo7.0.4-0-32bit-ccd1f64.image) and I want to run them in a 64-bit macOS (BigSur 11.4 now). I don't use Pharo Launcher but I tried downloading the corresponding 32-bit VM with ZeroConf curl https://get.pharo.org/64/vm70 | bash And launching those images always result in the classic error: This interpreter (vers. 68021) cannot read image file (vers. 6521) Is there any Docker solution/example for this? Cheers, HernÃ¡n

1 0

ZnServer multi-tenanting
by vinref＠gmail.com Sept. 14, 2021

Sept. 14, 2021

Hello I am planning some web apps, each of which at least initially will have a modest amount of traffic. Therefore it makes sense to use one image to run them all at the same time. I can do in a straightforward way from the delegate: ``` (ZnServer startOn: 1701) ``` ``` delegate: (ZnDefaultServerDelegate new ``` ``` at: '/' put: 'shop'; ``` ``` at: 'shop' put: [ :req | self serveShopPages: req ]; â¦) ``` and then: ``` #serveShopPages: aRequest ``` ``` | host | ``` ``` host := self getHostDetails: aRequest. ``` ``` â¦ ``` and ``` #getHostDetails: aRequest ``` ``` âLook in a class-side collection for cached host details.â ``` It is cumbersome though because each slot of the routing table I have to fetch the host details, but it is not too onerous. Most of the content will be static so I can cache it on the web-cache (nginx, ATS etc). Has anyone had any experience with multi-tenanting a ZnServer? It is hard to test the scaling as it depends on 1001 different things. Vince

1 0

Breakpoint in a DoIt method
by Jesus Mari Aguirre Sept. 11, 2021

Sept. 11, 2021

I need to set breakpoints in a source code compiled using > aCompiledMethod := self class compiler > source: source; > noPattern: true; > context: thisContext; > requestor: self; > bindings: self bindings; > compileDoit This compiled method has noPattern so it is executed as MyClass>>DoIt: I want to set a breakpoint programmatically, so a tried: Breakpoint removeAll. > breakpointList do:[ :aBreakpointIndex | > breakpoint := Breakpoint > breakOnAST: ( aCompiledMethod ast statements at: 2 ) > inObject: MyClassInstance. > breakpoint enable]. and executing it doesn't rises Break Exception > result:= compiledMethod > valueWithReceiver: MyClassInstance > arguments:{MyClassInstance}. It seems the breakpoint is installed because if I try to see the breakpoints folder inspecting MyClassInstance, the debugger raises errorKeyNotFound: key #DoIt: not Found in method dictionary. Any ideas?

1 0

Internships global link at ETS
by stephane ducasse Sept. 11, 2021

Sept. 11, 2021

> Begin forwarded message: > > From: Christopher Fuhrman <christopher.fuhrman(a)etsmtl.ca> > Subject: Fwd: Le programme de stage de recherche Globalink accepte encore les candidatures d'Ã©tudiants / Globalink Research Internship is still accepting student applications > Date: 11 September 2021 at 01:03:43 CEST > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>, Anne Etien <anne.etien(a)univ-lille.fr>, Nicolas ANQUETIL <nicolas.anquetil(a)inria.fr>, Vincent Aranega <vincent.aranega(a)inria.fr> > > --------- Forwarded message --------- > From: noreply_globalink <noreply_globalink(a)mitacs.ca <mailto:noreply_globalink@mitacs.ca>> > Date: Fri, Sep 10, 2021, 18:46 > Subject: Le programme de stage de recherche Globalink accepte encore les candidatures d'Ã©tudiants / Globalink Research Internship is still accepting student applications > To: christopher.fuhrman(a)etsmtl.ca <mailto:christopher.fuhrman@etsmtl.ca> <christopher.fuhrman(a)etsmtl.ca <mailto:christopher.fuhrman@etsmtl.ca>> > > > English version below <> > > Bonjour, <> > > Comme vous pouvez sÃ»rement le prÃ©sumer, le programme SRG est Ã©galement possible grÃ¢ce aux expÃ©riences positives et par la promotion du programme par nos participants. Ainsi, nous vous demandons svp de partager ce courriel avec vos collÃ¨gues/dâautres chercheurs ou chercheuses/vos connaissances. Ceci dans votre Ã©tablissement ou dans lâun de nos Ã©tablissements admissibles au programme SRG. > > Le programme deÂ stage de recherche Globalink, <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mitac…> qui offre un projet de recherche de 12 semaines dans des Ã©tablissements dâenseignement canadiens aux Ã©tudiantÂ·es exceptionnelÂ·les de premier cycle de lâÃ©tranger, accepte encore les candidatures des Ã©tudiantÂ·es. > > Les Ã©tudiantÂ·es approuvÃ©Â·es se rendront au Canada entre mai et octobre 2022, oÃ¹ ils travailleront avec unÂ·e professeurÂ·e superviseurÂ·e et dâautres chercheuses et chercheurs de leur Ã©tablissement dâenseignement dâaccueil. Les stagiaires de recherche Globalink bÃ©nÃ©ficient des avantages suivants: > > Â· un billet dâavion aller-retour pour le Canada (le montant varie selon le pays dâorigine); > Â· une allocation pour les frais de subsistance et les frais accessoires (le montant varie selon le pays dâorigine); > Â· lâinscription Ã des activitÃ©s du secteur privÃ© et Ã des cours de perfectionnement professionnel. > > Le site Web de notre Stage de recherche Globalink <https://can01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.mitacs…> contient de nombreuses informations sur les conditions d'admissibilitÃ© et la maniÃ¨re de postuler. Vous pouvez aussi en apprendre sur les expÃ©riences vÃ©cues par nos ancienÂ·esÂ participantÂ·esÂ de SRG <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mitac…>. > > Vous connaissez peut-Ãªtre une personne, qui connait une autre personne qui pourrait sâintÃ©resser Ã participer Ã notre programme en 2022. Veuillez svp nous aider Ã faire la promotion du programme SRG. Ceci augmentera nos volumes de candidatures, ce qui augmentera Ã©galement vos chances dâÃªtre jumelÃ©Â·e Ã unÂ·e candidatÂ·e de lâun des pays/rÃ©gions admissibles. > > > La date limite de dÃ©pÃ´t des candidatures est le 22 septembre 2021, Ã 13h PST. > > Si vous avez des questions au sujet du programme, communiquez avec nous Ã lâadresse assistance(a)mitacs.ca <mailto:assistance@mitacs.ca>. > > Merci, > > > > > > Avis de confidentialitÃ©â¯: Ce message courriel ainsi que tout fichier qui y est joint sont de nature confidentielle et peuvent constituer une information privilÃ©giÃ©e; il est envoyÃ© Ã lâintention exclusive de son ou de ses destinataires. Toute utilisation, divulgation, distribution ou copie de ceux-ci par une autre personne est strictement interdite. Si vous nâÃªtes pas le destinataire prÃ©vu, veuillez en aviser immÃ©diatement lâexpÃ©diteur par retour de courriel et supprimer ou dÃ©truire toutes copies. > Confidentiality Notice: This email message and any attachments are confidential, may be privileged and are intended for the exclusive use of the addressee(s). Anyone else is strictly prohibited from using, disclosing, distributing or reproducing them. If you have received this communication in error, please notify the sender immediately by return email and delete or destroy all copies. > > > Hello professor, > > As you may be aware, the GRI program is also made possible by our participantsâ positive experiences and their own program promotion. We ask you to please distribute this email to fellow professors/researchers/academic acquaintances at your institution/eligible GRI institutions. > > The Globalink Research Internship <https://can01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.mitacs…>, which provides a 12-week research project at Canadian universities for high-achieving senior undergraduates from around the world, is still accepting student applications. > > Approved students will travel to Canada between May and October 2022, where they will work with a faculty supervisor and other researchers at their host universities. Globalink research interns receive: > > Â· Round-trip airfare to Canada (amount varies depending on country of origin) > Â· Stipend for housing and living expenses (amount varies depending on country of origin) > Â· Registration for industry events and professional development courses > > There is extensive information on our Globalink Research Internship <https://can01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.mitacs…> website, where you can read more about eligibility requirements and how to apply. You can also read about the experiences of our pastÂ GRI participants <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mitac…>. > > You may know someone, who knows someone, who may be interested in participating in our program in 2022. Please help us promote the GRI program; this will increase our application volumes and incidentally improve your chances of being matched to a top candidate from our eligible countries/regions. > > The application deadline is Septemberâ¯22, 2021, at 1 p.m. PT.â¯â¯ > > If you have any questions about the program, contact us at helpdesk(a)mitacs.ca <mailto:helpdesk@mitacs.ca>. > > Thank you, > > > > > > Confidentiality Notice: This email message and any attachments are confidential, may be privileged and are intended for the exclusive use of the addressee(s). Anyone else is strictly prohibited from using, disclosing, distributing or reproducing them. If you have received this communication in error, please notify the sender immediately by return email and delete or destroy all copies. > Avis de confidentialitÃ© : Ce message courriel ainsi que tout fichier qui y est joint sont de nature confidentielle et peuvent constituer une information privilÃ©giÃ©e; il est envoyÃ© Ã lâintention exclusive de son ou de ses destinataires. Toute utilisation, divulgation, distribution ou copie de ceux-ci par une autre personne est strictement interdite. Si vous nâÃªtes pas le destinataire prÃ©vu, veuillez en aviser immÃ©diatement lâexpÃ©diteur par retour de courriel et supprimer ou dÃ©truire toutes copies. > > > >

1 0

Re: Upgrade job
by Otto Behrens Sept. 9, 2021

Sept. 9, 2021

Thanks, Steph On Thu, 09 Sep 2021, 07:26 stephane.ducasse(a)free.fr, < stephane.ducasse(a)free.fr> wrote: > Hello > > I will distribute this announce to other lists. > if you encounter any problems related to Pharo itself (which should not be > the case please let us the consortium knows > so that it takes action. We are investigating Grease to see if there is a > mismatch with the new exception for the debugger. > > S > > > On 8 Sep 2021, at 19:45, Otto Behrens <otto(a)finworks.biz> wrote: > > > > Hi, > > > > We are running a seaside app on GemStone 3.4.1 and develop in Pharo 6.1. > > > > Is there someone out there who would be interested in taking on the job > of upgrading both GemStone, Pharo and Seaside to recent versions? This is > in our environment, with numerous databases, testing and dev environments. > > > > It would be preferable if the person (or people) understand Monticello, > Metacello and Seaside packages that work together. > > > > This would be on a contract basis until the project is complete. Please > contact me directly if you are interested. > > > > Kind regards > > Otto Behrens > > >

1 0

Upgrade job
by Otto Behrens Sept. 8, 2021

Sept. 8, 2021

Hi, We are running a seaside app on GemStone 3.4.1 and develop in Pharo 6.1. Is there someone out there who would be interested in taking on the job of upgrading both GemStone, Pharo and Seaside to recent versions? This is in our environment, with numerous databases, testing and dev environments. It would be preferable if the person (or people) understand Monticello, Metacello and Seaside packages that work together. This would be on a contract basis until the project is complete. Please contact me directly if you are interested. Kind regards Otto Behrens

1 0

The ideal font for Pharo
by tau Sept. 7, 2021

Sept. 7, 2021

I've been bothered by the assignement operator (:=) and the way the colon and the equal sign aren't verticaly aligned when coding in Pharo. So I began a quest to find a pharo-friendly font were the colon and equal sign are aligned. Turn out most monospaced fonts don't qualify but I did find the following fonts: * Fira Code (https://fontlibrary.org/en/font/fira-code) has a := ligature that doesn't work in Pharo. * Iosevka extended (https://fontlibrary.org/en/font/iosevka-extended) also has a := ligature that doen't work in Pharo. * Mononoki (https://fontlibrary.org/en/font/mononoki) has the two characters properly aligned but I dislike the appareance of that font. The @, in particular, looks like it comes from a low-resolution terminal from the early '80s. * Fantasque Sans Mono (https://fontlibrary.org/en/font/fantasque-sans-mono) has perfectly aligned colon and equal sign and moreover has a nice informal look. So, Fantasque Sans Mono is now my favorite font for coding in Pharo ð.

5 5

Fwd: DateInput5 in Seaside widget preinitialized value view
by Oswall Verny Arguedas C. Sept. 6, 2021

Sept. 6, 2021

Regarding dateInput5 in Seaside. How a previously initialized date can be displayed in the form's dateInput5 widget. I use a pre-initialized date type value that is a property of the object to render on the form. html label for: 'startDate'; with: 'Start Date: '. html dateInput5 on: #startDate of: self contract; id: 'startDate'; step: 1; title: 'Start Date'; value: self contrato startDate; required. Widget don't render date initialized. I can't get it to show up. Thanks, Oswall

1 0

Silly question about storing and displaying currency amounts?
by David Pennington Sept. 1, 2021

Sept. 1, 2021

Hi everyone. I have a little bank analysis package for my own use but having trouble displaying and storing amounts. I parse out a CSV file from the bank and convert the amounts from text to ScaledDecimal. I then store these into a STON file, which converts them back to text. I then read them in and convert them back to ScaledDecimal again. I am not used to ~Pharo have spent 24 years using VisualAge Smalltalk so I need a little bit of help because I am getting 1 Penny errors in the conversions. I can cope with this but I would like to get it right. Can anyone give me a simple means of managing, say, an amount like Â£76.49 from the bank so that it stops coming back to me as Â£76.48? David Totally Objects

8 9

Re: uFFI: Calling conventions?
by egarrulo Aug. 30, 2021

Aug. 30, 2021

>> Yesterday we have implemented the image side part in P10 to correctly Â Â honour the calling convention. Does this imply that uFFI doesn't work correctly on current images? Because uFFI should have been available since Pharo 8, according to the uFFI manual.Â Or is it a revamped implementation? >> On the other hand, you are asking about ThisCall. This calling Â Â conventionis only relevant in 32bits systems. What is your target Â Â system/library? Does it not exist as 64-bit library? Unfortunately it is a legacy library with no 64 bit version. No problem, because I can write a wrapper, yet I was wondering if Pharo offered any facilities to avoid that. Thank you for the information. ---------------------------------------------------------------------- > Message: 1 > Date: Thu, 26 Aug 2021 15:38:48 +0200 > From: "tesonep(a)gmail.com" <tesonep(a)gmail.com> > Subject: [Pharo-users] Re: uFFI: Calling conventions? > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Message-ID: > <CAM9-ED+DYAJdOF0GfBcypmV9cQqufmSzUmC51EaLRzS2ycsPWQ(a)mail.gmail.com> > Content-Type: multipart/alternative; > boundary="0000000000004711e205ca767def" > > Hi All, > The answer is yes and no. > Let's go step by step. > To declare the calling convention a class can override the method > #ffiCallingConvention. Returning a Symbol representing the Calling > Convention. > > Yesterday we have implemented the image side part in P10 to correctly > honour the calling convention. > I have implemented it for X86 but this can be easily extended to ARM32 > (ARM64 has a single calling convention). > If this fix is useful, it can be backported to P9. > > However, this only works for X86_64 as it depends on the new FFI > implementation. We still do not have an X86 32 bits VM, it is possible to > compile it from sources, but we are not distributing it. > > In X86_64 only exists the Windows and the GNU calling convention, we are > supporting both. > > On the other hand, you are asking about ThisCall. This calling convention > is only relevant in 32bits systems. What is your target system/library? > Does it not exist as 64-bit library? > > Thanks > > On Tue, Aug 24, 2021 at 9:33 PM egarrulo <egarrulo(a)gmail.com> wrote: > >> Hi all, >> >> I haven't found any information on calling conventions in the "Unified >> FFI - Calling Foreign Functions from Pharo" manual. What conventions are >> available, please? >> >> If the ThisCall[1] convention isn't supported, could it be implemented >> in code with some boilerplate? >> >> Thank you. >> >> -- >> >> [1] ThisCall works like StdCall, but the first parameter - the "this" >> pointer - is passed via the ECX register. >> >>

2 1