May 2022 - Pharo-users - lists.pharo.org

Re: SmaCC: Adding conditions to production rules

by Thierry Goubier

Dear Konrad, the answer to your question is : it isn't pssoble as is in SmaCC (it breaks the underlying tcomputation heory). In practice, there are various ways to do so, depending on the kind of grammar you are building (and whether or not your grammar has conflicts). Cleanest way is to do a check at the end of the action (check that all <opidentifiers> are equal in the action, reject if this is not the case). You can use, if your grammar has conflicts, the GLR mode and select the right interpretation or reject the input. Another approach is to change the state of the scanner based on your actions, and so trigger the right production rule by emitting different tokens for example (such as a <sameOpIndentifier> following an <opIdentifier>. Again, different ways to do that; SmaCC offers an easy path to scanner specialisation that is fully compatible with SmaCC code generation (i.e. no fear to loose your customisation). Hope this helps, Thierry Le lun. 23 mai 2022 Ã 01:01, Konrad Hinsen <konrad.hinsen(a)fastmail.net> a Ã©crit : > > Hi everyone, > > I am stuck with a problem in SmaCC (of which I am a newbie user). Hoping > for suggestions from experts, any kind of pointer is welcome! > > I have a production rule for infix operators: > > Term > : NonInfixTerm 'arg' (<opIdentifier> 'opName' NonInfixTerm 'arg') * {{InfixOpTerm}} > | NonInfixTerm > ; > > According to the syntax rules of my language, infix terms are valid only > if all <opIdentifier>s are equal. Otherwise parentheses must be used to > disambiguate, as the language has no precedence rules. > > How can I do this with SmaCC? I don't see how I could do it using the > basic features, but maybe with some tweaking on the Pharo side. > > Thanks in advance, > Konrad.

May 24, 2022

PDFtalk for Pharo - first fileOut

by christian.haider＠smalltalked-visuals.com

Hi Pharoers, as some of you know, there is a project on the way for porting the PDFtalk library from VisualWorks to non-namespaced Smalltalks [1]. Now, the first fileOut of the full PDFtalk library, including Values and tests, is available for Pharo [2]. The fileOuts should load into Pharo 10.0 (or 9.0, 8.0, 7.0 and 6.1) without errors. The files are about 5 MB in size and take around 6 to 10 minutes to load on my machine. There are lots of load warnings in the Transcript and many tests have errors, but all code loads and can be browsed and examined. The tool automatically rewrites namespaced names with prefixed globally unique names. This seems to work well and automates away much of the usual porting work. Now I am looking for a Pharoer with an interest in PDF and/or the transformation tool and some time at hand to pair up for some coding. This is an exiting project. Heads up - who wants to be part of this? Happy hacking, Christian [1] https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout [2] https://wiki.pdftalk.de/doku.php?id=portingblog#first_fileout_of_the_full_pd ftalk_for_pharo P.S. I hope that I am writing to the right list - apologies, if this is spam for you

May 23, 2022

Re: Bonjour Service Discovery App available, and FFI library interface help required!

by Stewart MacLean

Hi Yanni, Apologies for the late reply. I'm working on something else at the moment, but will consider this when I get back to it. Thanks for your suggestions! Cheers, Stewart On Tue, May 17, 2022 at 1:37 AM Yanni Chiu <yannix7db(a)gmail.com> wrote: > From Pharo, fork a shell to run something like âenv > /top/emphatic.txtâ. > Or capture studio in Pharo, instead of writing to a temp file. It could be > that a forkâed shell has a different environment than used by FFI. In that > case the env vars may already be available through methods in the image. > > For the env that runs Bonjour successfully, run the âenvâ somewhere in the > script that starts that server. Again, it is possible to have different > environments, but most likely the environment is inherited, so is the same. > HTH > > On Sun, May 15, 2022 at 6:23 PM Stewart MacLean <stewart(a)xtra.co.nz> > wrote: > >> Thanks for this suggestion Yanni. >> >> When you say "dump the environment variables", how do you go about doing >> that? >> >> Cheers, >> >> Stewart >> >> On Mon, May 16, 2022 at 9:18 AM Yanni Chiu <yannix7db(a)gmail.com> wrote: >> >>> One thing I usually try in these situations is to dump the environment >>> variables, then sort and compare for clues as to why one way works but not >>> the other. >>> >>> On Sun, May 15, 2022 at 4:37 PM Stewart MacLean <stewart(a)xtra.co.nz> >>> wrote: >>> >>>> Hi Jesus, >>>> >>>> Thank you for giving it a go! >>>> >>>> This is pretty much what I have been experiencing - all very difficult >>>> to troubleshoot unless you really know what you're doing at this level. >>>> Which I don't! >>>> >>>> Thanks again! >>>> >>>> Stewart >>>> >>>> On Mon, May 16, 2022 at 2:41 AM Jesus Mari Aguirre < >>>> jmariaguirre(a)gmail.com> wrote: >>>> >>>>> sorry... I can not! >>>>> >>>>> On Sun, May 15, 2022 at 4:40 PM Jesus Mari Aguirre < >>>>> jmariaguirre(a)gmail.com> wrote: >>>>> >>>>>> I've been trying to help but I can make it work, so sorry... >>>>>> I changed sdRef by several options (you have an ExternalAddress, >>>>>> firstly I changed by DNSServiceRef externalNew pointer, and getHandle but >>>>>> nothing changed) >>>>>> Pharo gets hanged after the execution of the first callback >>>>>> defined at #browseServicesOf: >>>>>> [image: Captura de pantalla 2022-05-15 a las 16.30.44.png] >>>>>> >>>>>> I've tried to modify the signature to return void (end remove the >>>>>> last nil inside the callback block) >>>>>> [image: Captura de pantalla 2022-05-15 a las 16.30.29.png] >>>>>> >>>>>> Pharo dies executing the primitive primCallcackReturn >>>>>> >>>>>> [image: Captura de pantalla 2022-05-15 a las 16.27.35.png] >>>>>> >>>>>> I hope it helps you in any way >>>>>> >>>>>> >>>>>> On Sun, May 15, 2022 at 2:52 AM Stewart MacLean <stewart(a)xtra.co.nz> >>>>>> wrote: >>>>>> >>>>>>> Hi Esteban, >>>>>>> >>>>>>> That is a very good point! >>>>>>> >>>>>>> Please see >>>>>>> https://github.com/StewMacLean/Bonjour/blob/master/README.md for >>>>>>> version two of the readme that includes some screenshots etc. >>>>>>> >>>>>>> If anyone can make this work, you can! (Thanks again for the Pango >>>>>>> api help). >>>>>>> >>>>>>> I'm so curious as to what the problem is. I've tried all sorts of >>>>>>> combinations! >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Stew >>>>>>> >>>>>>> On Wed, May 11, 2022 at 8:52 PM Esteban Lorenzano <estebanlm(a)netc.eu> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, Steward, >>>>>>>> >>>>>>>> I do not have my mac around right now, but... >>>>>>>> it would help if you put also some code on how you expect the thing >>>>>>>> to work and what you expect to happen :) >>>>>>>> >>>>>>>> Esteban >>>>>>>> >>>>>>>> On May 11 2022, at 3:38 am, Stewart MacLean <stewart(a)xtra.co.nz> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Ok, after bashing my head against the Spinning Wheel of Death for >>>>>>>> ages trying to use FFI to interface to the Bonjour service discovery >>>>>>>> library, I've done it another way using essentially the same design >>>>>>>> framework, but scraping the command line output from dns-sd with the help >>>>>>>> of OSSubProcess. This is on a MacOS/M1/Monterey, Pharo 10 setup. >>>>>>>> >>>>>>>> This works nicely, but I would still like to get to the bottom of >>>>>>>> why the FFI doesn't work for this. So I've made all the code available on >>>>>>>> https://github.com/StewMacLean/Bonjour. You can either download a >>>>>>>> preloaded image/changes or use Metacello to download and install into a >>>>>>>> fresh P10 image. >>>>>>>> >>>>>>>> Once downloaded, it will select the openApp for the command line >>>>>>>> interface to run. To run the library interface you need to do the same >>>>>>>> thing, in that class - please refer to the read me and browse the code. >>>>>>>> >>>>>>>> I'd really appreciate any help I can get to get this working. I >>>>>>>> think it would make a great demonstration app for FFI usage once running. >>>>>>>> Please sing out with any questions etc. >>>>>>>> >>>>>>>> Thanks! >>>>>>>> >>>>>>>> Stew MacLean >>>>>>>> >>>>>>>>

May 22, 2022

SmaCC: Adding conditions to production rules

by Konrad Hinsen

Hi everyone, I am stuck with a problem in SmaCC (of which I am a newbie user). Hoping for suggestions from experts, any kind of pointer is welcome! I have a production rule for infix operators: Term : NonInfixTerm 'arg' (<opIdentifier> 'opName' NonInfixTerm 'arg') * {{InfixOpTerm}} | NonInfixTerm ; According to the syntax rules of my language, infix terms are valid only if all <opIdentifier>s are equal. Otherwise parentheses must be used to disambiguate, as the language has no precedence rules. How can I do this with SmaCC? I don't see how I could do it using the basic features, but maybe with some tweaking on the Pharo side. Thanks in advance, Konrad.

May 22, 2022

Re: MIDI Interface?

by Stewart MacLean

Hi Antoine, For some reason your message below didn't come to me, I just "stumbled" across it. Thanks for the link to your work, it looks interesting. For now, I'm focused on the "plumbing", and this will be a great help with getting the FFI library going and I'll share my thoughts along the way! I've just started porting my dusty VisualWorks MidiAccessLayer that utilises PortMidi and RtMidi. Once I've got it in shape I'll be glad to share it with you. Cheers, Stewart Hello Stewart, Indeed I am working on PortMidi C library binding on Pharo. For now, the code I wrote contains an object that represents the C library and you can use its methods to try some MIDI stuff. I added several layers to these methods to make it easier to use. You can also create what I call scores which are sequences of notes and play them either separately or add them in an object called Prestation that is able to play several scores at the same time. You can find the code on GitHub : https://github.com/pharo-contributions/pharo-sound . Do not hesitate to tell me what you think about it ! Antoine On Thu, May 19, 2022 at 2:23 AM stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > Antoine can you reply to Stewart? > > > On 16 May 2022, at 01:03, Stewart MacLean <stewart(a)xtra.co.nz> wrote: > > Hi Santiago, > > Thanks for this. My primary interest at the moment is interfacing with > Midi. > > The sound stuff looks interesting, even if it is not quite my cup of tea > music wise :) > > How far has your student got with the PortMidi bindings? As a first step, > as I can get a precompiled library via homebrew I thought I'd start by > migrating my VisualWorks PortMidi bindings - are they able to share this to > get me started? > > I have built a Midi Access Layer (in VisualWorks) which layers over both > RtMidi and PortMidi, which I had working on Windows quite a while ago. This > maybe useful? > > Cheers, > > Stewart > > On Sun, May 15, 2022 at 11:48 PM Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com> wrote: > >> Hi all! >> In inria we are working with an student on the bindings of PortMIDI in >> Pharo, and having some exchanges with an italian Dj that uses pharo for >> live-performances (https://www.youtube.com/watch?v=yBK0UpalBfk) >> >> We are trying to recover, in the long term the things in >> https://github.com/pharo-contributions/Sound, since there are awesome! >> >> If you have ideas feel free to share them! >> >> Santiago >> >> El dom, 15 may 2022 a las 6:07, Stewart MacLean (<stewart(a)xtra.co.nz>) >> escribiÃ³: >> >>> Hi all, >>> >>> Just wondering what the current state of interfaces to MIDI within Pharo >>> are? >>> >>> I gather that there was one (SoundScores that used primitives), but that >>> seems to have disappeared... >>> >>> Cheers, >>> >>> Stewart >>> >> >

May 20, 2022

Re: Please check older Issue tracker entries!

by Marcus Denker

> On 20 May 2022, at 12:10, Kasper Osterbye <kasper.osterbye(a)gmail.com> wrote: > > One meta-issue is that some issues might be raised in Pharo, but should be raised in some sub-project (Spec, Iceberg, Microdown, â¦). > > I for one has been working mostly in Microdown, and would not obviously discover an issue regarding Microdown raised in the Pharo project. Perhaps it is just I who is sluppy. > The problem is that discovery is hardâ¦ that is, to know where to put the issue. We should maybe be better at then opening issues in the sub projects as part of the daily issue tracker check. Marcus

May 20, 2022

Re: Please check older Issue tracker entries!

by Kasper Osterbye

One meta-issue is that some issues might be raised in Pharo, but should be raised in some sub-project (Spec, Iceberg, Microdown, â¦). I for one has been working mostly in Microdown, and would not obviously discover an issue regarding Microdown raised in the Pharo project. Perhaps it is just I who is sluppy. Best, Kasper > On 18 May 2022, at 08.50, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > One problem with a public issue tracker: it accumulates lots of issuesâ¦ > > This sadly means that issues will not be looked at one by oneâ¦ there are > just too many. > > One thing that is interesting to do is to check the issue that *you* submitted. > > - Is the issue still relevant? > - is the title good and in sync with the issue? > - Has it been fixed already ? (it happens!) > > Then, for every issue there is a ânext stepâ. It can be a good thing to spell out > very explicitly what the next step is âWe need to create a Pull Request for the > suggested fixâ. > > Or maybe what is needed is a summary of the huge discussion in the > issue tracker entry. > > Another idea: try to find others to help. E.g. > > - send a mail to the mailinglist. > - ask on discord. > > Maybe you can find a small group that works on this issue together. > > > > Marcus > > >

May 20, 2022

Re: MIDI Interface?

by antoine.delaby＠inria.fr

Hello Stewart, Indeed I am working on PortMidi C library binding on Pharo. For now, the code I wrote contains an object that represents the C library and you can use its methods to try some MIDI stuff. I added several layers to these methods to make it easier to use. You can also create what I call scores which are sequences of notes and play them either separately or add them in an object called Prestation that is able to play several scores at the same time. You can find the code on GitHub : https://github.com/pharo-contributions/pharo-sound . Do not hesitate to tell me what you think about it ! Antoine

May 20, 2022

Re: MIDI Interface?

by stephane ducasse

Antoine can you reply to Stewart? > On 16 May 2022, at 01:03, Stewart MacLean <stewart(a)xtra.co.nz> wrote: > > Hi Santiago, > > Thanks for this. My primary interest at the moment is interfacing with Midi. > > The sound stuff looks interesting, even if it is not quite my cup of tea music wise :) > > How far has your student got with the PortMidi bindings? As a first step, as I can get a precompiled library via homebrew I thought I'd start by migrating my VisualWorks PortMidi bindings - are they able to share this to get me started? > > I have built a Midi Access Layer (in VisualWorks) which layers over both RtMidi and PortMidi, which I had working on Windows quite a while ago. This maybe useful? > > Cheers, > > Stewart > > On Sun, May 15, 2022 at 11:48 PM Santiago Bragagnolo <santiagobragagnolo(a)gmail.com <mailto:santiagobragagnolo@gmail.com>> wrote: > Hi all! > In inria we are working with an student on the bindings of PortMIDI in Pharo, and having some exchanges with an italian Dj that uses pharo for live-performances (https://www.youtube.com/watch?v=yBK0UpalBfk <https://www.youtube.com/watch?v=yBK0UpalBfk>) > > We are trying to recover, in the long term the things in https://github.com/pharo-contributions/Sound <https://github.com/pharo-contributions/Sound>, since there are awesome! > > If you have ideas feel free to share them! > > Santiago > > El dom, 15 may 2022 a las 6:07, Stewart MacLean (<stewart(a)xtra.co.nz <mailto:stewart@xtra.co.nz>>) escribiÃ³: > Hi all, > > Just wondering what the current state of interfaces to MIDI within Pharo are? > > I gather that there was one (SoundScores that used primitives), but that seems to have disappeared... > > Cheers, > > Stewart

May 18, 2022

Re: [Pharo-dev] Re: Please check older Issue tracker entries!

by Sebastian Jordan Montano

Yes, thank you Marcus! Sebastian Jordan ----- Mail original ----- > De: "serge stinckwich" <serge.stinckwich(a)gmail.com> > Ã: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Cc: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > EnvoyÃ©: Mercredi 18 Mai 2022 11:51:30 > Objet: [Pharo-dev] Re: Please check older Issue tracker entries! > Thank you Marcus for your effort to engage more people from the community on > managing the issue tracker entries more efficiently ð > Regards, > > Sent from my iPhone > >> On 18 May 2022, at 14:50, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> ï»¿Hi, >> >> One problem with a public issue tracker: it accumulates lots of issuesâ¦ >> >> This sadly means that issues will not be looked at one by oneâ¦ there are >> just too many. >> >> One thing that is interesting to do is to check the issue that *you* submitted. >> >> - Is the issue still relevant? >> - is the title good and in sync with the issue? >> - Has it been fixed already ? (it happens!) >> >> Then, for every issue there is a ânext stepâ. It can be a good thing to spell >> out >> very explicitly what the next step is âWe need to create a Pull Request for the >> suggested fixâ. >> >> Or maybe what is needed is a summary of the huge discussion in the >> issue tracker entry. >> >> Another idea: try to find others to help. E.g. >> >> - send a mail to the mailinglist. >> - ask on discord. >> >> Maybe you can find a small group that works on this issue together. >> >> >> >> Marcus >> >>

May 18, 2022