Example:
# Stage 1: Load the project on an empty image, in this case this is a
development image (should change to use a minimal image)
FROM basmalltalk/pharo:7.0-image AS loader
COPY load-project.st ./
RUN pharo Pharo.image load-project.st --save --quit
# Stage 2: Copy the resulting Pharo.image
eftomi wrote
> I found the "ultimate" place where strings are being preparedfor INSERT
> INTO clause - this happens in String>>#glorpPrintSQLOn:. Not soeasy to
> parametrize at a first glance. Maybe withWideString>>#glorpPrintSQLOn: but
> I'm not sure how other platforms would behappy.An
Thanks Tomaz! This is great :)
Nice docs too!
> El 15 oct 2019, a las 21:36, eftomi escribió:
>
> Dear all,
>
> A working prototype of PharoADO is now available at
> https://github.com/eftomi/pharo-ado. I'd be glad if you can find the time to
> test it and report your observations to this
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
--- Begin Message ---
Hello,
Im busy with this project: https://github.com/RoelofWobben/Die
Now I also want to try to add a DieHandler and a Die together.
And I heared you can use the visitor pattern to solve this.
As far as I understand the pattern I have to make a new class which
contains
(1) Be very clear in your design about which objects are shared and
which are not.
(2) Immutable objects can be shared safely. Mutable ones are much
much harder to work with.
(3) Lazy initialisation does not work well in concurrent programming,
*except* when you are
constructing an immutable
