- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Moose-dev] Re: [Pharo-users] [ANN] Lan.d.s Alpha: All Along the Language Tower

by Nick Papoylias

That was good to know. I updated the site with* one-click direct* *(non-recurring) alternative*: *PayPal.Me for Lands* <https://www.paypal.me/npapoylias> https://npapoylias.gitlab.io/lands-project/Support/ *"Alternatively you can make a direct (non-recurrent) contribution * *through paypal.me <http://paypal.me>: PayPal.Me for Lands <https://www.paypal.me/npapoylias>. Adding "Lands Support" * *as a note, plus the e-mail and address you would wish to * *receive your perks on"* Cheers, Nick On Sun, Mar 17, 2019 at 5:26 PM Nick Papoylias <npapoylias(a)gmail.com> wrote: > > > On Sun, Mar 17, 2019 at 2:18 PM StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Hi nick >> >> I wanted to support your chapters via paypal but it asked me about my >> visa and I would like >> to pay via my paypal account. Do you know if this is possible? >> > > Thanx Stef ! > > *Through patreon, this seems to be required for recurrent payments:* > > > https://support.patreon.com/hc/en-us/articles/115001917686-Why-do-I-need-to… > > There are 2 alternatives through that might not have this requirement: > > *Alternative 1, through the Paypal button (if you did not try already):* > > *Step1,* from: https://npapoylias.gitlab.io/lands-project/Support/ > > Hit the PayPal button. > > *Step2*: And then in the Paypal screen, hit PayPal pay. > > *Alternative 2, directly from your PayPal dashboard:* > > "*Pay for goods or services* No fee for you. The recipient pays a fee." > > *using my e-mail address:* npapoylias(a)gmail.com <npapoylias(a)gmail.com> > > Adding in the note a message like: "Lands Support" so that it is > distinguishable > form other transactions. > > *Let me know if you encounter any problems, so that I contact them, if > necessary.* > And update the site, for ways to support without credit-card required. > > Best, > > Nick > > Else can you send me your pp account? >> >> Stef >> >> On 17 Mar 2019, at 10:21, Nick Papoylias <npapoylias(a)gmail.com> wrote: >> >> *Dear friends ! * >> >> I am quite excited to announce the availability of an alpha version >> of my latest work around *Parsing and Programming Languages *at: >> >> https://npapoylias.gitlab.io/lands-project/ >> >> Accompanied by *~ 30 min of transcribed eye-candy:* >> >> https://www.youtube.com/playlist?list=PLIjPQnRzAKVHABG1-oTvwWc3Gj1Z4C91B >> >> Backed by* a crowdfunding campaign ! *To get the *book and stable >> release * >> successfully out of the door: >> >> https://www.patreon.com/lands_project >> https://npapoylias.gitlab.io/lands-project/Support/ >> >> *Click, download, watch, enjoy !* If you like what you see, support the >> project ! Tiers >> start *from 5 and 10 euros per chapter for individuals.* Companies >> supporting >> the project can get >> *6 to 12 days of consultancy, on-site workshops and other perks.* >> ================= >> >> *What is all about ??* >> >> *Lan.d.s is a new solution for language design.* From >> *general purpose languages *like *Lise* (short for (list (embedding)) to >> *Domain-Specific Languages using the MOODs framework*, and everything >> else in between. >> Lan.d.s is build around the formalism of >> *Multi-Ordered Grammars, which are a possible alternative to CFGs and >> PEGs in wider use today.* >> >> Multi-ordered grammars (or simply MOGs) aim for a better exploration of >> ambiguity, >> recursion, ordering and associativity during language design. They can be >> *parsed using the Gray Algorithm. *After parsing in order to ease the >> production of executable code >> Lan.d.s introduces the *Abstract Syntax Language (ASL)*, which is an OO >> solution for compile-time meta-programming. Finally in order to promote >> language extension and re-use, Lan.d.s employs >> *GrammarTraits, as units of composition for both MOG rules and ASL >> actions.* >> >> ================= >> >> Some random highlights for the impatient: >> >> >> ** Object subclass: #Prediction uses: Future syntax* >> >> ** Languages are everywhere, they are all around you, even now in this >> very sentence.* >> >> ** Study SICP with a Xerox flavor, while re-inventing some Bell-labs >> utilities.* >> >> ** TOC-Board, the TOC for your next talk ;)* >> >> >> Enjoy ! >> <Theory-and-Applications-Of-Multi-Ordered-Grammars.pdf> >> <Lands-Alpha-All-Along-The-Language-Tower.png> >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >

March 17, 2019

Re: [Pharo-dev] Roassal Animations

by Serge Stinckwich

Most of the animations are available in the Roassal3 code: https://github.com/ObjectProfile/Roassal3 On Sun, Mar 17, 2019 at 7:23 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > Who has seen these Roassal Animations on Twitter recently ? > > These are crazy cool and super slick. > > Is there a place where they are all collected, maybe with their code ? > > Sven > > > -- Serge Stinckwic âhâ Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) âSorbonne University (SU) French National Research Institute for Sustainable Development (IRD)â U âniversity of YaoundÃ© Iâ, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich â

March 17, 2019

Re: [Pharo-dev] ZnBufferedReadStream and #upToAll:

by ducasse

> On 17 Mar 2019, at 18:28, Benoit St-Jean <bstjean(a)yahoo.com> wrote: > > If that was the case, then it makes no sense to implement #upTo: but not #upToAll: , right ???? Indeed :) > > On 2019-03-17 10:37, ducasse wrote: >> Was there a conscious decision not to include the #upToAll: method onZnBufferedReadStream?. This method is really useful for parsing files -- finding sub-patterns of bytes, etc. Perhaps #upToAll: is not the idiomatic way to do this, but I found it very useful to use in the plain old ReadStream classes. >> I imagine that sven did not add it because on infinite stream it does not make sense. >> Now it would be good to see how we can have useful extensions. But I let this to sven. >

March 17, 2019

Re: [Pharo-dev] Roassal Animations

by ducasse

> On 17 Mar 2019, at 19:23, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > Who has seen these Roassal Animations on Twitter recently ? Me :) > These are crazy cool and super slick. > > Is there a place where they are all collected, maybe with their code ? We should ask milton and alex > Sven > >

March 17, 2019

Roassal Animations

by Sven Van Caekenberghe

Hi, Who has seen these Roassal Animations on Twitter recently ? These are crazy cool and super slick. Is there a place where they are all collected, maybe with their code ? Sven

March 17, 2019

Re: [Pharo-dev] ZnBufferedReadStream and #upToAll:

by Benoit St-Jean

If that was the case, then it makes no sense to implement #upTo: but not #upToAll: , right ???? On 2019-03-17 10:37, ducasse wrote: > Was there a conscious decision not to include the #upToAll: method onZnBufferedReadStream?. This method is really useful for parsing files -- finding sub-patterns of bytes, etc. Perhaps #upToAll: is not the idiomatic way to do this, but I found it very useful to use in the plain old ReadStream classes. > I imagine that sven did not add it because on infinite stream it does not make sense. > Now it would be good to see how we can have useful extensions. But I let this to sven.

March 17, 2019

Re: [Pharo-dev] ZnBufferedReadStream and #upToAll:

by Sven Van Caekenberghe

Eric, Someone wrote a clean implementation of #upToAll: that does not use #position: - I forgot who - but it can be found in ZnCharacterReadStream>>#upToAll: I guess this could be copied over to ZnBufferedReadStream. The main reason that I was against #upToAll: was the implementation using #position: - but what Stef says it also very true: if you do not find what you are looking for, you will read up to end, which is not possible with network streams - you will hang. I also try to minimise the stream API in the newer streams, which is hard because the existing API is so broad. Personally, I never needed #upToAll: during parsing (I also always limit lookahead to 1). I am really curious why you need it ? Most users of #upToAll: search for CRLF, for which I would use a line reader class like ZnLineReader or ZnFastLineReader. Another point is that, if you absolutely need everything that is in the classic ReadStream (which is much more than a stream as it holds a collection of all its elements), in most cases, you could read your content first (assuming it is of known size) and wrap a classic stream around it. Sven > On 17 Mar 2019, at 15:45, Eric Gade <eric.gade(a)gmail.com> wrote: > > Thanks Stef, > > I imagine that sven did not add it because on infinite stream it does not make sense. > > Just to clarify my earlier email, I got here was by calling `'/path/to/some/file' asFileReference binaryReadStream` which responds with the ZnBufferedReadStream. I expected to be able to use something like #upToAll: to find binary-formatted headers etc within some encoding structure. It's entirely possible that this was the wrong expectation! > > On Sun, Mar 17, 2019 at 10:38 AM ducasse <stepharo(a)netcourrier.com> wrote: > Hi eric > > > Hi all, > > > > Was there a conscious decision not to include the #upToAll: method onZnBufferedReadStream?. This method is really useful for parsing files -- finding sub-patterns of bytes, etc. Perhaps #upToAll: is not the idiomatic way to do this, but I found it very useful to use in the plain old ReadStream classes. > > I imagine that sven did not add it because on infinite stream it does not make sense. > Now it would be good to see how we can have useful extensions. But I let this to sven. > > > > Sub-question: if I wanted to implement something like this and make a PR, would I be submitting to the Pharo dev repository or the Zinc repository? > > Right now to sven repo. In the future we want to have better tools to sync back from a project to its components. > > Stef > > > > -- > > Eric > > > > > > -- > Eric

March 17, 2019

Re: [Pharo-dev] [Moose-dev] Re: [Pharo-users] [ANN] Lan.d.s Alpha: All Along the Language Tower

by Nick Papoylias

On Sun, Mar 17, 2019 at 2:18 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi nick > > I wanted to support your chapters via paypal but it asked me about my visa > and I would like > to pay via my paypal account. Do you know if this is possible? > Thanx Stef ! *Through patreon, this seems to be required for recurrent payments:* https://support.patreon.com/hc/en-us/articles/115001917686-Why-do-I-need-to… There are 2 alternatives through that might not have this requirement: *Alternative 1, through the Paypal button (if you did not try already):* *Step1,* from: https://npapoylias.gitlab.io/lands-project/Support/ Hit the PayPal button. *Step2*: And then in the Paypal screen, hit PayPal pay. *Alternative 2, directly from your PayPal dashboard:* "*Pay for goods or services* No fee for you. The recipient pays a fee." *using my e-mail address:* npapoylias(a)gmail.com <npapoylias(a)gmail.com> Adding in the note a message like: "Lands Support" so that it is distinguishable form other transactions. *Let me know if you encounter any problems, so that I contact them, if necessary.* And update the site, for ways to support without credit-card required. Best, Nick Else can you send me your pp account? > > Stef > > On 17 Mar 2019, at 10:21, Nick Papoylias <npapoylias(a)gmail.com> wrote: > > *Dear friends ! * > > I am quite excited to announce the availability of an alpha version > of my latest work around *Parsing and Programming Languages *at: > > https://npapoylias.gitlab.io/lands-project/ > > Accompanied by *~ 30 min of transcribed eye-candy:* > > https://www.youtube.com/playlist?list=PLIjPQnRzAKVHABG1-oTvwWc3Gj1Z4C91B > > Backed by* a crowdfunding campaign ! *To get the *book and stable release > * > successfully out of the door: > > https://www.patreon.com/lands_project > https://npapoylias.gitlab.io/lands-project/Support/ > > *Click, download, watch, enjoy !* If you like what you see, support the > project ! Tiers > start *from 5 and 10 euros per chapter for individuals.* Companies > supporting > the project can get > *6 to 12 days of consultancy, on-site workshops and other perks.* > ================= > > *What is all about ??* > > *Lan.d.s is a new solution for language design.* From > *general purpose languages *like *Lise* (short for (list (embedding)) to > *Domain-Specific Languages using the MOODs framework*, and everything > else in between. > Lan.d.s is build around the formalism of > *Multi-Ordered Grammars, which are a possible alternative to CFGs and PEGs > in wider use today.* > > Multi-ordered grammars (or simply MOGs) aim for a better exploration of > ambiguity, > recursion, ordering and associativity during language design. They can be > *parsed using the Gray Algorithm. *After parsing in order to ease the > production of executable code > Lan.d.s introduces the *Abstract Syntax Language (ASL)*, which is an OO > solution for compile-time meta-programming. Finally in order to promote > language extension and re-use, Lan.d.s employs > *GrammarTraits, as units of composition for both MOG rules and ASL > actions.* > > ================= > > Some random highlights for the impatient: > > > ** Object subclass: #Prediction uses: Future syntax* > > ** Languages are everywhere, they are all around you, even now in this > very sentence.* > > ** Study SICP with a Xerox flavor, while re-inventing some Bell-labs > utilities.* > > ** TOC-Board, the TOC for your next talk ;)* > > > Enjoy ! > <Theory-and-Applications-Of-Multi-Ordered-Grammars.pdf> > <Lands-Alpha-All-Along-The-Language-Tower.png> > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > http://www.synectique.eu / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev >

March 17, 2019

[Pharo 8.0] Build #146: 2843-Clean-Navigation-code

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #146 was: SUCCESS. The Pull Request #2844 was integrated: "2843-Clean-Navigation-code" Pull request url: https://github.com/pharo-project/pharo/pull/2844 Issue Url: https://pharo.fogbugz.com/f/cases/2843 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 17, 2019

[Pharo 8.0] Build #145: 2817-distinguish-between-instance-side-and-class-side-in-method-template

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #145 was: SUCCESS. The Pull Request #2819 was integrated: "2817-distinguish-between-instance-side-and-class-side-in-method-template" Pull request url: https://github.com/pharo-project/pharo/pull/2819 Issue Url: https://pharo.fogbugz.com/f/cases/2817 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 17, 2019