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
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
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
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
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,
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
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
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
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
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
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
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
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
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
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
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
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
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.
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
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
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 (=
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
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
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
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
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)
… and after the second block #map
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:
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
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
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
--- 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
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
Thanks Stef and Offray,
those are really interesting pieces, I am going to look into definitely.
Cheers!
Steffen
Offray Vladimir Luna Cárdenas via Pharo-users schrieb am Dienstag, 5. August
2025 21:32:41 (+02:00):
Super cool! Nice to have more tools like in the the Pharo toolkit. I did som
101 - 134 of 134 matches
Mail list logo
