Re: [Pharo-users] Porting Transducers to Pharo

;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On May 31, 2017, at 10:32 AM, Steffen Märcker <merk...@web.de> wrote: Thanks for the encouraging response! First question: Which is the recommended (friction free) way to exchange code between

Re: [Pharo-users] Porting Transducers to Pharo

f code and it feels ad-hoc in Smalltalk. I really prefer square := Map function: #squared. take := Take number: 1000. Because I know that I can read it and understand it. From that perspective I prefer Xtreams. Stef On Wed, May 31, 2017 at 2:23 PM, Steffen Märcker <merk...@web.de>

Re: [Pharo-users] Porting Transducers to Pharo

Uhr, schrieb Stephane Ducasse <stepharo.s...@gmail.com>: Hi steffen On Wed, May 31, 2017 at 2:23 PM, Steffen Märcker <merk...@web.de> wrote: Hi, I am the developer of the library 'Transducers' for VisualWorks. It was formerly known as 'Reducers', but this name was a poor choi

Re: [Pharo-users] Porting Transducers to Pharo

create the package in SmalltalkHub or Github based on your files/changeset. Do you have a github and/or SmalltalkHub account? Best, Phil On Tue, Jun 6, 2017 at 1:08 PM, Steffen Märcker <merk...@web.de> wrote: Hi! If the need arises, we could of course factor the compact notation out into

[Pharo-users] Porting Transducers to Pharo

Hi, I am the developer of the library 'Transducers' for VisualWorks. It was formerly known as 'Reducers', but this name was a poor choice. I'd like to port it to Pharo, if there is any interest on your side. I hope to learn more about Pharo in this process, since I am mainly a VW guy. And

Re: [Pharo-users] Porting Transducers to Pharo

educe as defined right now" - reduce: aBlock init: "value "reduce starting with an initial value" - reduce: aReduction "reduce with block and value from a reduction" Kind regards, Steffen Best, Phil On Wed, Jun 7, 2017 at 11:29 AM, Steffen Märcker <merk...@web.de&

Re: [Pharo-users] Porting Transducers to Pharo

In fact, I moved from Mocketry to DoubleAgents quite some time ago... =) Am .06.2017, 23:04 Uhr, schrieb Denis Kudriashov : 2017-06-07 22:04 GMT+02:00 p...@highoctane.be : I read your note about DoubleAgents for the tests, well, yeah this one we do

Re: [Pharo-users] Porting Transducers to Pharo

>> I do not see why this is needed. To my eyes the compact notation >>> goes against readibility of code and it feels ad-hoc in Smalltalk. >>> >>> >>> I really prefer >>> >>> square := Map function: #squared. >>> take := Take number:

Re: [Pharo-users] Porting Transducers to Pharo

Hi! If the need arises, we could of course factor the compact notation out into a separate package. Good idea [...] I do not want to help promoting a syntax that alienates me (and others because other people reported the saem to me). I understand. Btw, I'd really, really appreciate if

Re: [Pharo-users] Porting Transducers to Pharo - Name Clash

n Am .05.2017, 14:23 Uhr, schrieb Steffen Märcker <merk...@web.de>: Hi, I am the developer of the library 'Transducers' for VisualWorks. It was formerly known as 'Reducers', but this name was a poor choice. I'd like to port it to Pharo, if there is any interest on your side. I hope to lear

Re: [Pharo-users] Porting Transducers to Pharo

Hi Phil, Tell me how it goes for you. I played a bit with Iceberg in Pharo, managed to check out the repository, and load Transducers-Core. As a bit of a surprise, multiple packages show up in the SystemBrowser; one for each method category, e.g., Transducers-accessing and

Re: [Pharo-users] Porting Transducers to Pharo

com>: As you know I experimented with that a while ago. My code is at http://smalltalkhub.com/#!/~cdlm/Experiments/source On 31 May 2017 at 15:00, Sven Van Caekenberghe <s...@stfx.eu> wrote: > On 31 May 2017, at 14:23, Steffen Märcker <merk...@web.de> wrote: > >

Re: [Pharo-users] Porting Transducers to Pharo

Thanks for the encouraging response! First question: Which is the recommended (friction free) way to exchange code between VW and Pharo? Cheers! Steffen Am .05.2017, 16:22 Uhr, schrieb Alexandre Bergel : I second Sven. This is very exciting! Let us know when you

Re: [Pharo-users] Porting Transducers to Pharo

should produce packages with also a configuration and published them on smalltalkhub or git and in the MetaRepository. You can also add package comments On Sat, Jun 3, 2017 at 10:29 PM, Steffen Märcker <merk...@web.de> wrote: Dear all, attached are updated file-outs. I fixed a couple o

Re: [Pharo-users] Stream API

Hi, Are transducers the subject of your thesis ? No. Transducers is my side project. I've implemented a package for VisualWorks. Unfortunately, I did not finish the port to Pharo yet, simply due to a lack of time. Originally, transducers evolved in the clojure community. I figured, the

Re: [Pharo-users] Stream API

Hi! Yes, I agree, Xtreams is much better (but steep learning curve). I just wanted to point out that my contributions in Zn streams focus and better/simpler byte/character IO. Yes, and it is really nice. Interesting how many users we have in system for general streams? (created on

Re: [Pharo-users] Stream API

.eu>: On 14 Nov 2017, at 16:00, Steffen Märcker <merk...@web.de> wrote: Hi, <---Schnitt---> No. Transducers is my side project. I've implemented a package for VisualWorks. Unfortunately, I did not finish the port to Pharo yet, simply due to a lack of time. Originally, t

Re: [Pharo-users] Stream API

Short: No. =) Actually, the <~ notation was originally proposed by another Smalltalker on the vwnc list. The idea was that <~ visualizes the flow into the variable, which I find nice (see first expression). However, I do understand that this alienates others. Hence, I am non-religious

Re: [Pharo-users] Stream API

Please note, the port on GitHub is not the most recent version. I had trouble porting it to Pharo and code exchange in general. For now it's unfinished due to a lack of time. Am .11.2017, 16:30 Uhr, schrieb Steffen Märcker <merk...@web.de>: I forgot to mention, that the most recen

Re: [Pharo-users] Binary Decision Diagram Package in Smalltalk

>Subject: Re: [Pharo-users] Binary Decision Diagram Package in Smalltalk > >Hi Andrew, Steffen, > >2017-11-07 13:10 GMT+01:00 Prof. Andrew P. Black <bl...@cs.pdx.edu>: > >> On 28 Oct 2017, at 17:37 , Steffen Märcker <merk...@web.de> wrote: >> >> Does that

Re: [Pharo-users] Binary Decision Diagram Package in Smalltalk

r, schrieb Thierry Goubier <thierry.goub...@gmail.com>: Le 07/11/2017 à 23:00, Steffen Märcker a écrit : I am not familiar with the literature on scanners. May I ask you about some details on the "for all characters" algorithms you are referring to? The two main ones avail

Re: [Pharo-users] Binary Decision Diagram Package in Smalltalk

c when parsing inputs containing utf-8 characters. On Sat, Oct 28, 2017 at 1:46 PM, Steffen Märcker <merk...@web.de> wrote: I see. What is the task in detail? Are some of the set fixed or known in advance? What's the argument against a bitset-based solution? Cheers, Steffen Am 27. Oktober 2

Re: [Pharo-users] Set Rounding mode for IEEE floating point operations

*bump* I guess there no way to do this now. But maybe a VM guy can give me how difficult it might be to extend the VM accordingly. Best, Steffen Am .01.2018, 12:27 Uhr, schrieb Steffen Märcker <merk...@web.de>: Hi, is there any way to set the rounding mode for IEEE floating

Re: [Pharo-users] Set Rounding mode for IEEE floating point operations

Hi Henry, [...] it might be possible to try to do this with FFI only? If I understand you correctly, I could use FFI to call an external lib to perform the actual computation according to the rounding mode, right? In this case I'd be worry about the performance impact of many FFI calls.

Re: [Pharo-users] Set Rounding mode for IEEE floating point operations

/upper bounds. Best, Steffen Am .05.2018, 12:50 Uhr, schrieb Serge Stinckwich <serge.stinckw...@gmail.com>: On Wed, May 23, 2018 at 11:47 AM Steffen Märcker <merk...@web.de> wrote: *bump* I guess there no way to do this now. But maybe a VM guy can give me how difficult it might

Re: [Pharo-users] Set Rounding mode for IEEE floating point operations

I actually made progress: It works like a charm! Basically, I implemented the same code as you. Testing is straightforward (using the constant values from libc): current := LibC fegetround. LibC fesetround: FE_DOWNWARDS. v1 := 1.0/10.0. LibC feesetround: FE_UPWARDS. v2 := 1.0/10.0.

Re: [Pharo-users] Set Rounding mode for IEEE floating point operations

< serge.stinckw...@gmail.com> wrote: On Thu, May 24, 2018 at 10:31 AM Steffen Märcker <merk...@web.de> wrote: I actually made progress: It works like a charm! Basically, I implemented the same code as you. Testing is straightforward (using the constant values from libc): curre

Re: [Pharo-users] Set Rounding mode for IEEE floating point operations

. But before I want to make sure it a) works as expected and b) does not cause some nasty side effects. Bye, Steffen Am .05.2018, 12:26 Uhr, schrieb Serge Stinckwich : On Thu, May 24, 2018 at 12:27 PM Steffen Märcker wrote: Hi, now I've observed the same issue. It might be related

Re: [Pharo-users] Smalltalk-76 Demo

Cool stuff!Am .04.2018, 04:22 Uhr, schrieb Bernardo Ezequiel Contreras :https://youtu.be/NqKyHEJe9_w-- Bernardo E.C.Sent from a cheap desktop computer in South America.

Re: [Pharo-users] Binary Decision Diagram Package in Smalltalk

Dear Andrew, I didn't find time to answer earlier. Some time ago, I was looking for a (MT)BDD package in ST as well. I didn't found one. So the only two options left are 1) implementing a new BDD lib in ST and 2) doing FFI to some existing lib, e.g. CUDD, Sylvan, Jinc I'd prefer 2) since

Re: [Pharo-users] Binary Decision Diagram Package in Smalltalk

so we do not want to >rely on external libraries. > >On Fri, Oct 27, 2017 at 1:54 PM, Steffen Märcker <merk...@web.de> >wrote: >> Dear Andrew, >> >> I didn't find time to answer earlier. Some time ago, I was looking >for a >> (MT)BDD package in ST as well

Re: [Pharo-users] Pharo 7 streams API

pecific part of it while being such generic that it helps in other places as well. Just pointing it out so there isn't a perception they are competing to solve same problem and only one should be selected. Herby On July 3, 2018 3:57:21 PM GMT+02:00, "Steffen Märcker" wr

Re: [Pharo-users] Pharo 7 streams API

I think, streams and functional composition match up nicely and transducers are a way to do this. I've introduced them earlier on this list. (I hesitated to weight into the discussion, as I won't have time to work on the Pharo port of Transducers until October.) Let me give a simplified

Re: [Pharo-users] Pharo 7 streams API

rby On July 3, 2018 3:57:21 PM GMT+02:00, "Steffen Märcker" wrote: I think, streams and functional composition match up nicely and transducers are a way to do this. I've introduced them earlier on this list. (I hesitated to weight into the discussion, as I won't have time to

Re: [Pharo-users] Set Rounding mode for IEEE floating point operations

Yes, I was considering this in the context of some approximation algorithms. Maybe one of the VM experts here could comment on the possibility to implement that? Am .01.2018, 10:00 Uhr, schrieb Serge Stinckwich <serge.stinckw...@gmail.com>: On Mon, Jan 15, 2018 at 12:27 PM, S

Re: [Pharo-users] looking for another iterator :)

Hi! this is straightforward with Transducers, e.g., (Take n: 5) <~ #(1 2 3 4 5 6 7 8). or #(1 2 3 4 5 6 7 8) transduce take: 5. The different primitives like take, drop, map, filter, etc. are composable and do not generate intermediate representations. The bad news are, that the Pharo

Re: [Pharo-users] looking for another iterator :)

Hi! No stress is good news! - what is the API in terms of vocabulary (ie drop the same as reject) These are the operations implemented so far. |= means "satisfies", i.e., evaluate to true. Drop drop first n elements DropWhile drop first elements |= a block Filter* pick

[Pharo-users] Set Rounding mode for IEEE floating point operations

Hi, is there any way to set the rounding mode for IEEE floating point operations? Maybe something like Double roundToMinusInfWhile: [... code goes here ...]Double roundToZeroWhile: [... more code here ...] If not, is it possible to add this behavior, e.g., via a custom primitive? Best,

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

6521/, too. Am .10.2018, 17:02 Uhr, schrieb Sean P. DeNigris : Steffen Märcker wrote I did the following: 1) Download and start Pharo 6.1 stable via the launcher. 2b) Attempt to install PP2 via the scripts from GitHub: Metacello new baseline: 'PetitParser2'; repositor

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

xceeds SmallInteger maxVal, doesn't it? Best, Steffen Am .10.2018, 17:10 Uhr, schrieb Steffen Märcker : I am using MacOS 10.13.6 and the 32bit VM: Pharo 6.0 Latest update: #60546 ... the String in about is wrong, it should be 6.1. I installed it via the launcher as "Official Distribution

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

-ci.org/kursjan/petitparser2/builds/438358467 On Thu, Oct 11, 2018 at 8:13 PM Steffen Märcker wrote: Reading the code of PetitParser, I wonder why PPRepeatingParser initializes 'max' with SmallInteger maxVal instead of some notion of infinity, like Float infinity (and PP2RepeatingNode as well). If I

[Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

comprehensive tool set. Best, Steffen Am .10.2018, 18:06 Uhr, schrieb milton mamani : Hi you can use https://github.com/ObjectProfile/Pharo2VW Cheers, Milton El sáb., 13 oct. 2018 a las 12:38, Steffen Märcker () escribió: Hi, I gave PetitParser 2 a try and I am pretty impressed by the results

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

o hear your thoughts on the porting matter. Best, Steffen Am .10.2018, 16:06 Uhr, schrieb James Foster : We will have the same issue porting PP2 to GemStone and look forward to suggestions. On Oct 22, 2018, at 4:40 AM, Steffen Märcker wrote: Hi Jan, I am trying to port PP2 to VW an

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

t 8:13 PM Steffen Märcker wrote: Reading the code of PetitParser, I wonder why PPRepeatingParser initializes 'max' with SmallInteger maxVal instead of some notion of infinity, like Float infinity (and PP2RepeatingNode as well). If I understand the code correctly, PParser>>min: fails if the number

[Pharo-users] Persistant Taskbar Previews

Hi, Using Pharo 6.1 for some hours, I ended up with quite a few previews from (long gone) taskbar entries that refuse to go away. They seem to be PanelMorphs. How do I get rid of them? Best, Steffen

Re: [Pharo-users] Persistant Taskbar Previews

process, probably left over from some debugging. Kill one using the Process Browser. But this is just a blind guess. On 13 Oct 2018, at 04:51, Ben Coman wrote: On Fri, 12 Oct 2018 at 18:57, Steffen Märcker wrote: Hi, Using Pharo 6.1 for some hours, I ended up with quite a few previews

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

be interested in trying this out? Cheers, Doru On Oct 4, 2018, at 10:46 PM, Steffen Märcker wrote: I gave Xtreams-Parsing and PetitParser a shot and like to share my findings.[*] The task was to parse the modelling language of the probabilistic model checker PRISM. I've written a grammer

[Pharo-users] [ANN] PEG Grammar, Compiler and Parser for PetitParser2

as PetitParser2-PEG in the PublicStore (VW) and on GitHub (https://github.com/merkste/petitparser2/tree/PEG). Best, Steffen Am .10.2018, 22:46 Uhr, schrieb Steffen Märcker : I gave Xtreams-Parsing and PetitParser a shot and like to share my findings.[*] The task was to parse the modelling language

[Pharo-users] [ANN] PetitParser2 for VisualWorks (Was: [vwnc] Parsing in Smalltalk)

Hi, I am happy to announce that I've just finished an initial port of (the impressive) PetitParser2 (https://github.com/kursjan/petitparser2) to VisualWorks. It is available in the Public Store. The port consists of 4 bundles: * PetitParser2 * PetitParser2-Tests * PetitParser2-Smalltalk

Re: [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

to Pharo2VW. We reviewed and accepted your PullRequests. Alexandre On Oct 19, 2018, at 6:29 AM, Steffen Märcker wrote: Nevermind, I figured it out easily. Must been blind before. Many thanks to the Iceberg team, the tool works like a charm in 6.1! Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker

Re: [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

Nevermind, I figured it out easily. Must been blind before. Many thanks to the Iceberg team, the tool works like a charm in 6.1! Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker : Hi, I tried the tool yesterday and found some hickups. After opening issues on GitHub, I wonder how I can

Re: [Pharo-users] library to chain select:/collect:/ ... via cascade

Hi, indeed, transducers provided a way to achieve this, e.g. #(12 7 'a' nil #(0)) pipe filter: #notNil; filter: #isNumber; map: #squared; filter: #even; into: OrderedCollection. But this feature is deprecated, as it was not that useful. The preferred

Re: [Pharo-users] library to chain select:/collect:/ ... via cascade

Another important difference is that no intermediate collections are built. In contrast, chaining x enumeration statements #select:, #collect:, etc. iterates x times over the collection elements and builds x-1 intermediate collections. Am .10.2018, 11:59 Uhr, schrieb Steffen Märcker : Hi

Re: [Pharo-users] VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))

:29 AM, Steffen Märcker <mailto:merk...@web.de> > wrote: Nevermind, I figured it out easily. Must been blind before. Many thanks to the Iceberg team, the tool works like a charm in 6.1! Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker <mailto:merk...@web.de> >: <---Schnitt--->

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

Am .10.2018, 20:14 Uhr, schrieb Steffen Märcker : Dear all, I have two questions regarding parsing frameworks. 1) Do you have any insights on the performance of SmaCC VS Xtreams Parsing VS PetitParser? 2) Has anybody started to port PetitParser 2 from Pharo to VW? Is it worth the effort

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

Hi Ben! Thanks for your report Steffen. Nice to see such comparisons even when a bit apples & oranges. Will you be implementing those "additional verification and normalization steps" ? It seems they have an exponential or power impact on times. I certainly will. Meanwhile, I have some more

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

Hi Doru! I assume that you tried the original PetitParser. PetitParser2 offers the possibility to optimize the parser (kind of a compilation), and this provides a significant speedup: https://github.com/kursjan/petitparser2 Would you be interested in trying this out? Yes, I'd like to

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

of syncing PP2 to VW2. Cheers, Jan [1]: https://kursjan.github.io/petitparser2/pillar-book/build/Chapters/memoization.html On Fri, Oct 5, 2018, 13:26 Steffen Märcker wrote: Hi Doru! > I assume that you tried the original PetitParser. PetitParser2 offers > the possibility to op

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

Can you give more details? IIRC I have PP2 loaded in several 6. I did the following: 1) Download and start Pharo 6.1 stable via the launcher. 2a) Attempt to install PetitParser2 via the CatalogBrowser: "Information There was an error while trying to install PetitParser2.

[Pharo-users] Parsing in VW

Dear all, I have two questions regarding parsing frameworks. 1) Do you have any insights on the performance of SmaCC VS Xtreams Parsing VS PetitParser? 2) Has anybody started to port PetitParser 2 from Pharo to VW? Is it worth the effort? Sorry for cross-posting, I thought this might

Re: [Pharo-users] Updating singletons

Hi Konrad, sorry, I might have misread your question such that it was about updating references to an obsolete object. However, there is another fun possibility to figure out that a change happened that does not involve configuration - though, a bit hacky. ;-) You could write the

Re: [Pharo-users] [ANN] PetitParser (1) has been migrated to Github

Great, thanks a lot! Steffen Am .12.2018, 10:22 Uhr, schrieb Julien : Hello, I just finished the migration of PetitParser (1) on Github: https://github.com/moosetechnology/PetitParser . I created a release v1.9.2 which mirrors latest

Re: [Pharo-users] Playing with Pharo 7

Great! Am .11.2018, 21:47 Uhr, schrieb Cyril Ferlicot D. : Le 26/11/2018 à 16:57, Konrad Hinsen a écrit : Thanks for the pointer! Unfortunately all the documentation there assumes way more familiarity with Smalltalk than I have. And even a lot of familiarity with Metacello itself, as the

Re: [Pharo-users] Updating singletons

Have you considered to yield (an) proxy object(s) instead of the actual Singleton in uniqueInstance? This way it suffices to update the proxy with each update of the code. Am 3. Januar 2019 15:36:27 MEZ schrieb Ben Coman : >On Thu, 3 Jan 2019 at 20:01, Konrad Hinsen via Pharo-users <

Re: [Pharo-users] Documentation on Traits

Nice. Do you know where to find details on stateful traits and slots? I am familiar with stateless traits and wonder how state is incoeporated and how conflicts are handled. Best, Steffen Am 9. Januar 2019 15:21:09 MEZ schrieb Konrad Hinsen : >Cyril Ferlicot writes: > >> There is

Re: [Pharo-users] Documentation on Traits

Maybe I missed that part: Can conflicts with slots occur? The section on conflicts only mentions methods as cause. Do you have a pointer to a slots documentation? Am 9. Januar 2019 20:32:51 MEZ schrieb "Cyril Ferlicot D." : >Le 09/01/2019 à 18:49, Steffen Märcker a écrit : &g

Re: [Pharo-users] Symbol equality method #= - weird condition in the Pharo sourcecode

Is it consistent with the definition of #= in String such that 'aSymbol = aString' iff 'aString = aSymbol'? Sorry, I don't have an image at hand. Am 1. März 2019 18:40:11 MEZ schrieb Sven Van Caekenberghe : >Why ? Please explain ... > >> On 1 Mar 2019, at 18:02, David T. Lewis wrote: >> >> On

Re: [Pharo-users] Why can't a Bag answer as a dictionary?

This is exactly how I think and feel about bags. Thanks Richard. Am .03.2019, 01:35 Uhr, schrieb Richard O'Keefe : To me, a bag is first and foremost a multiset. Yes, it's a collection, but it's not *just* a collection. It's a very specific kind of collection with a very salient

Re: [Pharo-users] [ANN] Iterators

Hi Julien, nice work! Could you please tell how your approach is related to transducers from the user perspective and technically? (https://github.com/Pharophile/Transducers) Your example suggests that the API is quite similar to the data flow API of transducers. Let me show your example using

Re: [Pharo-users] Lazy Streams - was: Re: Set >> collect:thenDo:

Hi, I really think we should have an efficient way to chain operations on collections and alike. In my personal opinion, this should be backed by transducers, as they decouple the operations from the type the data source and sink. Hence they are applicable to different collection types, streams

Re: [Pharo-users] Set >> collect:thenDo:

I think this thread indicates that the selector #collect:thenDo: may indeed cause some missunderstanding given standard semantics of #collect:. Is there any reason not to use a different one, such as #map:thenDo:, to make the difference clearer? A nice side effect could be a new automatic

Re: [Pharo-users] Set >> collect:thenDo:

Surprise! The selector #collect:thenDo: strongly suggests that it behaves just as #collect: then #do:. But as #collect: usually means map + aggregate in the reveiver type, I'd expect the input to the do block to be deduped already. At least it is an easy to miss source of subtle bugs. Maybe an

Re: [Pharo-users] Concurrency Best Practices + Tests

I can definitely second all the points. If you want to verify your design formally, Vereofy (http://www.vereofy.de) is another model checker that focuses on communication and coordination. Best, Steffen Am .10.2019, 08:49 Uhr, schrieb Richard O'Keefe : (1) Be very clear in your design about

Re: [Pharo-users] BlockClosure

Looks nice! Just my two cents. To make function comopostion work with multiple aruments, I implemented * as: BlockClosure class>>* first ^ComposedFunction first: first second: self And use a dedicated class to make multiple arguments work: ComposedFunction>>value: arg ^second

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

Dear Sean, thanks for bringing this up and for the interesting link [1]. I'll have a look. Meanwhile, I am still on both lists. ;-) Steffen Märcker wrote I wrote a PetitParserGenerator that takes the DSL and builds a PetitParser. I don't know how I could've missed this gem! I hope

Re: [Pharo-users] [ANN] uFFI Booklet v1.0

Great! Thanks for the effort of putting this example-driven booklet together! Steffen Guillermo Polito schrieb am Wed Feb 12 2020 10:30:31 GMT+0100 (Mitteleuropäische Normalzeit): Hi all, We have been working a lot in the last months in the documentation of uFFI, and we are happy to

[Pharo-users] Hi-DPI Support

Hi, I'd like to ask about the state of Hi-DPI support for Pharo. I already found two related GitHub issues which where inconclusive so far. Does the discussion take place elsewhere? If so, where? If not: - What is the current state? - Does a plan exist how to get there? - What are the missing

Re: [Pharo-users] Rosetta Code

would like to have a zip file to serve as a shortcut for developing Pharo versions, you'd be very welcome. On Fri, 17 Apr 2020 at 21:31, Steffen Märcker wrote: Hi, some of you might have hear of Rosetta Code, a Wiki that presents solutions to standard programming tasks in various languages. I

[Pharo-users] Rosetta Code

Hi, some of you might have hear of Rosetta Code, a Wiki that presents solutions to standard programming tasks in various languages. I figured that in many categories no Smalltalk/Pharo solutions are shown. Maybe we can contribute some pieces from time to time? I started with the following:

Re: [Pharo-users] Can it do this way ?

Maybe this is a naive question, but can you just split the task into the following two? 1. Check whether whether the string is syntactically an ISBN number. This can be done, e.g., using a regex. 2. Check the the check character. Calculate the check character from the (now to be known)

Re: [Pharo-users] Can it do this way ?

'\d{1,7} \d{1,7} \d{1,7} [0-9X]'. grouped := (dashes , '|' , spaces) asRegex. ^(aString matchesRegex: nonGrouped) or: [(aString matchesRegex: grouped) and: [aString size = (10 + 3)]] Best, Steffen Am .09.2020, 19:01 Uhr, schrieb Steffen Märcker : Hi, after reading the link and

Re: [Pharo-users] Can it do this way ?

Hi Richard and Roelof, thanks for your comprehensive answer. I brought up Regex only to point out alternative solutions. Another one is the following using transducers, where Tee works like the tee command from the command line. IsbnValidator>>isValidIsbn: aString | length countChars

Re: [Pharo-users] Can it do this way ?

Hi, after reading the link and some additional sources, it turns out that a valid ISBN-10 has either no separators or four blocks separated by either dashes or spaces: Group-Publisher-Title-CheckDigit Assuming Regex11 (and that I made no mistake), the following should do the trick:

Re: [Pharo-users] Can it do this way ?

No problem. I am not knowledgeable about isbn numbers. At which places may a dash occur? Kind regards, Steffen 07.09.2020 16:18:22 Roelof Wobben via Pharo-users : > Op 6-9-2020 om 10:07 schreef Steffen Märcker: >> Maybe this is a naive question, but can you just split

[Pharo-users] Re: order of execution

Hi, don't forget to read the expression from left to right: currTotal := prevTotal + (prevTotal := currTotal). 5 1 43 2 1. the current value (X) of prevTotal is fetched. 2. the current value (Y) of currTotal is fetched 3. prevTotal is assigned currTotal which

[Pharo-users] Re: [Pharo-dev] [Ann] Pharo new version available & mooc needs subtitle translaters

Hi! Is it still possible to attend / watch the Mooc? The page (https://www.fun-mooc.fr/courses/course-v1:inria+41024+session01/about) tells that registration ended on nov 07. Or do I miss other ways to access the course and its material? Best, Steffen Am .11.2020, 18:02 Uhr, schrieb

[Pharo-users] Re: [Pharo-dev] [Ann] Pharo new version available & mooc needs subtitle translaters

*rofl* Well, I was not even close ... Thanks! Am .11.2020, 11:04 Uhr, schrieb jtuc...@objektfabrik.de : YEs, you miss the year ;-) It says 2021 Am 10.11.20 um 10:13 schrieb Steffen Märcker: Hi! Is it still possible to attend / watch the Mooc? The page (https://www.fun-mooc.fr/courses

[Pharo-users] Re: Rounding in Floats

Typo: FP should read floating point and not fixed point. Steffen Märcker schrieb am Dienstag, 15. Juni 2021 08:47:24 (+02:00): > Have you considered using fixed-point arithmetic? For example: > 7.1s2 roundTo: 0.1s2 > > The rule of thumb I stick to is to use FP only if I know the

[Pharo-users] Re: Rounding in Floats

Have you considered using fixed-point arithmetic? For example: 7.1s2 roundTo: 0.1s2 The rule of thumb I stick to is to use FP only if I know the inaccuracies won't bite me. Funny enough, both 7.1 and 0.1 are already not accurately representable as floats. (And by coincidence, I prepared exam

[Pharo-users] Fwd: [vwnc] Exception in Regex11 1.4.6

below. Furthermore, you might have an opinion on allowing more escape sequences in character classes, don't you? Kind regards, Steffen - Weitergeleitete Nachricht - Von: Steffen Märcker An: 'VWNC' Betreff: Re: [vwnc] Exception in Regex11 1.4.6 Datum: Thu Jun 24 2021 18:47:01 GMT+0200

[Pharo-users] Re: Fwd: [vwnc] Exception in Regex11 1.4.6

From: Steffen Märcker Sent: Tuesday, June 29, 2021 6:13:00 PM To: Any question about pharo is welcome Subject: [Pharo-users] Re: Fwd: [vwnc] Exception in Regex11 1.4.6 Dear all! I just checked and found that Regex in Pharo is indeed based on Regex11. It suffers from the same bug

[Pharo-users] Re: Fwd: [vwnc] Exception in Regex11 1.4.6

Dear all! I just checked and found that Regex in Pharo is indeed based on Regex11. It suffers from the same bug as the original. I'd like to bring the fix to Pharo. As a first-timer, where can I read about the procedure of contributing code? Kind regards, Steffen Steffen Märcker schrieb am

[Pharo-users] Re: Pharo 9 arbitrarily changes temporary variable names

Hi Robert, have you checked that you're seeing the code you've typed and not just decompiled methods? Best, Steffen Robert Briggs via Pharo-users schrieb am Montag, 27. Dezember 2021 11:43 (+01:00): Hi I define temporary variables in a method, e.g. |e r |, e.g. in a unit test, but

[Pharo-users] Run old 32-Bit image on 64-Bit macOS

Hi, I am looking for a way to run an old 32-Bit image on a modern Mac (Montery). Pharo launcher gives me the following error: Cannot run Prism Grammar (Pharo 6.1)! This image requires a 32-Bit VM to run and 32-Bit applications are not supported on this Operating System. Is there a way to run it

[Pharo-users] Re: [ANN] Pharo 10 released!

Congratulations to the new release. That's quite an impressive amount of changes and cleanups. Will the stable version be available in the PharoLauncher soon? Cheers, Steffen Esteban Lorenzano schrieb am Dienstag, 5. April 2022 12:39:44 (+02:00): Dear Pharo users and dynamic language

[Pharo-users] Re: [ANN] Pharo Launcher 3.0 released!

Hi Christophe, thanks, that's great news! [Downloading ...] Cheers! Steffen Christophe Demarey schrieb am Donnerstag, 14. April 2022 14:26:26 (+02:00): Hi all, Pharo Launcher 3.0 has just been released! It is available from http://pharo.org/download. It is based on latest Spec2 and Pharo

[Pharo-users] AST vs. Bytecode Interpreters

Hi folks! Today I found this interesting paper via Stefan Marr on the performance differences of ast vs. bytecode interpreters (for meta compilation): https://stefan-marr.de/downloads/oopsla23-larose-et-al-ast-vs-bytecode-interpreters-in-the-age-of-meta-compilation.pdf It was a really

[Pharo-users] Re: A question about #beginsWith: and #endsWith:

I can only fully agree to Richard's explanation. Also, not having the empty string pre/suf-fixing every string breaks the free monoid that describes concatenation of strings and forms the basis of regular expressions. In effect, this will lead to subtle inconsistencies. Hence, I consider this a

[Pharo-users] Re: A question about #beginsWith: and #endsWith:

an issue on the issue tracker Issue #11165 in https://github.com/pharo-project/pharo/issues/11165 Best, Kasper On 26 Apr 2022, at 12.11, Steffen Märcker wrote: I can only fully agree to Richard's explanation. Also, not having the empty string pre/suf-fixing every string breaks the fre

[Pharo-users] Re: A question about #beginsWith: and #endsWith:

Hi Kasper, I've thought about that approach too. But then asked myself whether it is more likely that there is code that relies on this bug than code where this went unnoticed and is therefore broken. What do the other think about that matter and the fix in Squeak? Best, Steffen Kasper

  1   2   >