I remember - way back in the dark ages - walking into a music store,
picking up a CD, and asking it to buy itself. Every single time, the
response was the same: nothing.
On Fri, Apr 16, 2021 at 10:07 AM Tim Mackinnon wrote:
> Its comforting to see that other have the same reaction as me - I
Its comforting to see that other have the same reaction as me - I agree with
the sentiment that you send messages to objects - and the naming of those
messages and their context is important.
and CD.buy - is at least a message to an object but as others have commented,
it highlights flaws in
Nope. Just stderr. It is continuing to happy at random times so it is obviously
connected to page requests. I have some logging in. Place so I have increased
that to try and help get to the point where it happens.
David
> On 16 Apr 2021, at 15:45, Davide Varvello via Pharo-users
> wrote:
>
Hi David,
Usually when the image crashes you'll find a crash.dmp file.
It's weird there isn't anything
Davide
Long Haired David wrote
> Sorry to but in here but I have just moved my Pharo/Seaside server
> software from my MacBookAir, where it has run without issue for the last
> couple of weeks,
Wow, I must be missing a whole lot of context in that discussion...
(instant reaction as well, lol)
- a product (CD, book, etc.) does not 'buy' - it can be bought, sure, but
it has no buying action. Even in another context a CD does not 'play'...
aMusicPlayer.play(aCD).
- However, a customer can
I saw a tweet about that, and I think that the example is misleading, maybe
intentionally so.
I don't think anybody would model it that way, in any case you'd have
aProduct.buy() or aProduct.addToCart(aCart).
If you think it with the typical dog.bark() it certainly makes more sense
than
Hi guys - someone pointed out this article from a UK colleague which seems to
be causing a flurry of discussion - but I always like the insights of this
group. I had an instant reaction when I read it - but curious what people here
think in 2021.
