[Pharo-users] Re: Foliage 2.1.0

Hi Stephane, both links to the example do not work: http://www.github.com/Pillar-markup/FoliageSample (from Foliage github page) https://github.com/FoliageSample (from your mail) Ciao, Steffen stephane ducasse via Pharo-users schrieb am Sonntag, 3. August 2025 15:33:38 (+02:00): Hello

[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 interesti

[Pharo-users] Packages

Hi, is there a way to create an empty package programatically, and how do I rename a package programmatically? Is there a documentation about packages and how exactly their naming scheme relates to tags? Kind regards, Steffen

[Pharo-users] Re: Porting from VW to Pharo

hrieb am Samstag, 6. Mai 2023 19:05:22 (+02:00): All references disentangled. Everything should be clean now. Happy hacking, Christian Von: Steffen Märcker Gesendet: Freitag, 5. Mai 2023 10:15 An: Any question about pharo is welcome Betreff: [Pharo-users] Re: Porting from VW to Pharo

[Pharo-users] Re: Porting from VW to Pharo

e in Pharo with Git, I don’t know much about that. Actually, I would also be interested in some guidelines to bake them into the transformations… If you are seriously interested, we could have an online session to hack around with it… Cheers, Christian Von:

[Pharo-users] Re: Picking neighbouring elements

… and after the second block #map

[Pharo-users] Re: Picking neighbouring elements

Coding in mail is not easy after all. SortedCollection>>greaterThan: contains a silly mistake from editing. At the end it should read:    ^[:y | y = x] dropWhileTrue   <~ [:i | self at: i]   <~ (index to: self size)

[Pharo-users] Re: Picking neighbouring elements

s sorted, we should use another algorithm. Assuming an ascending order with no random access, we'd change minimum to stop early: minimum := [:min :b | Stop result: b]. Kind regards, Steffen Richard O'Keefe schrieb am Freitag, 21. April 2023 05:33:44 (+02:00): successor o

[Pharo-users] Re: Picking neighbouring elements

pril 2023 05:33:44 (+02:00): successor of x in c = the smallest element of c that is larger than x min {y | y in c . y > x} predecessor of x in c = the largest element of c that is smaller than x max {y | y in c . y < x} On Thu, 20 Apr 2023 at 21:08, Steffen Märcker wrote: Dear Richard

[Pharo-users] Re: Picking neighbouring elements

Dear Richard, thanks for that additional piece. I'll put insert- on my list of possible variants. I think we come back to naming after the initial port is done and everyone can play with it. Generally, I made the observation to better be careful with names since it's too easy to alienate other o

[Pharo-users] Re: Project and package structure recommendations

st/GitHub-setup for generating the initial boilerplate of new projects. Regards, Gabriel On Wed, Apr 19, 2023 at 12:55 PM Steffen Märcker wrote: Hi, I'd like to ask for your advice or best practices regarding the package structure of a project. So far I have understood: - Iceberg can stor

[Pharo-users] Project and package structure recommendations

Hi, I'd like to ask for your advice or best practices regarding the package structure of a project. So far I have understood: - Iceberg can store multiple packages (project?) in a git repository - A package (or multiple?) and its dependencies is loaded via a baseline - A package can have flags (=

[Pharo-users] Re: Collection>>reduce name clash with transducers

ressions"? (MIT AI Memo 958A and 959A) Or his later SERIES package? (Appendix A of Common Lisp the Language, 2nd edition) On Fri, 14 Apr 2023 at 22:32, Steffen Märcker wrote: Hi Richard! Thanks for sharing your thoughts. There's a reason why #inject:into: puts the block argument

[Pharo-users] Re: Collection>>reduce name clash with transducers

r f| f := r := nil. anEnumerable do: [:each | r := f ifNil: [f := self. each] ifNotNil: [self combine: r with: each]]. f ifNil: [anEnumerable error: 'is empty']. ^r On Fri, 14 Apr 2023 at 05:02, Steffen Märcker wrote: The reason I came up with the

[Pharo-users] Re: Collection>>reduce name clash with transducers

touch multiple implementations of that message. Something I consider undesirabe. 3) Currently, I cannot think of a good name that is not too far away from what we're familiar with. Do you have some constructive comments and ideas? Kind regards, Steffen Steffen Märcker schrieb am Donnerstag, 13.

[Pharo-users] Re: Collection>>reduce naming

n/PACK.html On Fri, 14 Apr 2023 at 01:34, Steffen Märcker wrote: Hi Richard and Sebastian! Interesting read. I obviously was not aware of the variety of meanings for fold/reduce. Thanks for pointing this out. Also, in some languages it seems the same name is used for both reductions with an

[Pharo-users] Re: Comparison of blocks

that a block always has a reference to its outer context. Variables in copiedValues are not modified after block creation if I understand the class comment correctly, but variables in tempVector can, right? Best, Steffen Steffen Märcker schrieb am Donnerstag, 13. April 2023 15:14:16 (+02:00

[Pharo-users] Re: Collection>>reduce naming

led #inject:into:) So for me the Pharo methods #reduce: and #inject:into represent well what they are doing and they are well named. Cheers, Sebastian - Mail original - > De: "Steffen Märcker" > À: "Any question about pharo is welcome" > Envoyé: Mercredi 12 A

[Pharo-users] Re: Comparison of blocks

ion of #= for block contexts/closures you are almost certainly doing something dangerous. You are certainly doing something that is not portable. On Thu, 13 Apr 2023 at 18:55, Steffen Märcker wrote: Hi! In VisualWorks, blocks can be compared with each other. In Pharo the comparison just

[Pharo-users] Re: Porting from VW to Pharo

heers, Christian Von: Steffen Märcker Gesendet: Dienstag, 11. April 2023 17:52 An: Any question about pharo is welcome Betreff: [Pharo-users] Re: Porting from VW to Pharo Dear Christian and Richard, thanks for your answers. I'll try to go through the process step by step and

[Pharo-users] Comparison of blocks

Hi! In VisualWorks, blocks can be compared with each other. In Pharo the comparison just checks for Identity. Is this on purpose? For reference, that's how BlockClosure>>= is implemented in VW: = aBlockClosure ^aBlockClosure class = self class and: [method = aBlockClosure metho

[Pharo-users] Re: [vwnc] Block evaluation with n+1 arguments

Dear Richard, thanks for elaborating on your ideas. As I am still figuring out what works best, I'll give them a try. Especially the approach to let the source deal with passing the arguments to the block - though this requires more changes. The problem is NOT, as some commentators apparently

[Pharo-users] Collection>>reduce naming

Hi! I wonder whether there was a specific reason to name this method #reduce:? I would have expected #fold: as this is the more common term for what it does. And in fact, even the comment reads "Fold the result of the receiver into aBlock." Whereas #reduce: is the common term for what we call wit

[Pharo-users] Re: [vwnc] Block evaluation with n+1 arguments

Hi! First, thanks for your engaging answers Richard, Stephane and the others! The objective is to avoid unnecessary object creation in a tight loop that interfaces between a value source and a block that processes the values. - The source object returns multiple values as a tuple (for good reaso

[Pharo-users] Re: [vwnc] Block evaluation with n+1 arguments

mooc https://rmod-files.lille.inria.fr/DesignCoffeeClub/ForLearningLab/7-Lang-04-BlocksVsObjects.pdf On 6 Apr 2023, at 15:28, Steffen Märcker wrote: Hi! I want to evaluate a block an argument 'arg1' and additional n arguments given in an array 'args'. Th

[Pharo-users] Re: Block evaluation with n+1 arguments

r 6 2023, at 3:28 pm, Steffen Märcker wrote: Hi! I want to evaluate a block an argument 'arg1' and additional n arguments given in an array 'args'. The following code does the trick: block valueWithArguments: (Array with: arg1) , args. Is there a way to do this without the overh

[Pharo-users] Re: Porting from VW to Pharo

Pharo, Squeak, GemStone, and VAST. PDFtalk is quite complex and the porting rules are correspondingly complex. The Transform documentation does leave something to be desired. On Thu, Apr 6, 2023 at 8:22 AM Steffen Märcker wrote: Hi! this topic pops up from time to time on the mailing

[Pharo-users] Re: Porting from VW to Pharo

k (from VisualWorks) to Pharo, Squeak, GemStone, and VAST. PDFtalk is quite complex and the porting rules are correspondingly complex. The Transform documentation does leave something to be desired. On Thu, Apr 6, 2023 at 8:22 AM Steffen Märcker wrote: Hi! this topic pops up from time to time

[Pharo-users] Porting from VW to Pharo

Hi! this topic pops up from time to time on the mailing list. I want to port a number of packages to Pharo. I remember "Shaping" asking this for porting PDFtalk. 1. Is the workflow still up to date or is there a new way of doing things? 2. From what I understand so far, I just need the following

[Pharo-users] Re: A blog on graph algorithms library of Pharo

Hi Goutham, thanks for sharing that post. Looks interesting, indeed! Best, Steffen Guillermo Polito schrieb am Mittwoch, 5. April 2023 10:03:28 (+02:00): Hi Goutham! Thanks for the post! I like the concrete examples. I did not find them in the repo, I think pushing the examples as comment

[Pharo-users] Block evaluation with n+1 arguments

Hi! I want to evaluate a block an argument 'arg1' and additional n arguments given in an array 'args'. The following code does the trick: block valueWithArguments: (Array with: arg1) , args. Is there a way to do this without the overhead of creating a new Array? (How) Can I add additional #v

[Pharo-users] Re: ESUG 2023 Call for participation

Hi! Is there a firm submission deadline set yet? Ciao, Steffen stephane ducasse schrieb am Samstag, 11. Februar 2023 18:49:42 (+01:00): > ESUG 2023 Call for Presentations > 28.8.2023 to 01.9.2023 > Lyon France > https://esug.github.io > https://esug.github.io/2023-Con

[Pharo-users] Re: Recovering old images in mac

Is there a way to save / convert such an image to 64 Bit? Best, Steffen

[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

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

raised it as 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 s

[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 bu

[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 1

[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 lovers

[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: 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 whe

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

stian 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 a

[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 schri

[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

[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 ques

[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: [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 Hern

[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

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 sepa

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

]'. spaces := '\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är

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: IsbnVarifi

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 the task

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) syntactic

Re: [Pharo-users] Rosetta Code

tem. If anyone 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

[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: https

[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 pi

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 announ

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 t

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 value

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] 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 a

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 refacto

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] [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 t

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 "characteristic

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 F

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] 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 documentatio

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 accessor

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 < >pharo-user

Re: [Pharo-users] (no subject)

--- Begin Message --- Did you already try to measure the impaired overhead of a wrapper solution? It might very well be negligible in an otherwise purely symbolic computation. A hybrid solution might be - instead of wrapping each value - to add a single method to the value classes that wrap

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 rele

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 d

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--->

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

le 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 lan

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

on 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ä

[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 (d

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

be happy to 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 PP

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

: https://travis-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 PP2Repe

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] 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 wa

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

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

haros 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 re

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

d you 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

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

[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] [vwnc] Parsing in Smalltalk

7;-' [1]: https://travis-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 infin

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

etitions exceeds 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 "Offici

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';

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. Installatio

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

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 optimi

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 give

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 pr

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

t, Steffen 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

[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 inter

Re: [Pharo-users] Pharo 7 streams API

hing to solve more specific 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, "Steffe

Re: [Pharo-users] Pharo 7 streams API

should be selected. Herby 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 discussio

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 exa

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

aro 7. 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

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

.com> wrote: On Thu, May 24, 2018 at 10:31 AM Steffen Märcker 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): current := LibC fegetround. LibC fesetround: FE_DOW

  1   2   >