[Pharo-users] Re: About String and Symbol equality

2025-02-02 Thread Richard O'Keefe
Not that anyone else probably cares, but the ANSI standard says - for All objects x y, x = y if and only if y = x. The Smalltalk-80 mixup over String and Symbol violated this, ‘X’ = #x but #x ~= ‘x’. - two sequences are = iff they are the same size, corresponding elements are =, AND they are

[Pharo-users] Re: [Pharo-dev] About String and Symbol equality

2025-02-02 Thread Aik-Siong Koh
How did Pharo diverge from the other Smalltalks? Was it a good decision? stephane ducasse wrote: Hello people In Pharo (following Squeak tradition) a string is equals to its symbol representation. e.g. ’tintin’ = #tintin > true In other Smalltalk dialects this is not the case. We have been

[Pharo-users] Re: About String and Symbol equality

2025-02-02 Thread Jupiter Jones via Pharo-users
my 2c... There are arguments for and against any of the semantics decisions, so leaving those aside for greater minds... +1 GemStone Pharo and GemStone have long been an enviable workflow for “complex problems". They go together in a project, each providing a necessary part of the puzzle. Pha

[Pharo-users] About String and Symbol equality

2025-02-02 Thread stephane ducasse
Hello people In Pharo (following Squeak tradition) a string is equals to its symbol representation. e.g. ’tintin’ = #tintin > true In other Smalltalk dialects this is not the case. We have been working (sponsored by Lifeware) to support both semantics (yes this is a kind of

[Pharo-users] Re: "Book release: Application Building with Spec 2.0" — New blog post on all: objects all: theTime

2025-02-02 Thread giorgio ferraris
Thanks for writing the book, Stefan (and all the other guys) ciao giorgio On Sat, Feb 1, 2025 at 5:07 PM stephane ducasse wrote: > Thanks. > Writing this book was a daunting huge difficult exhausting task that took > me around 4 years or more. > > This publisher is managed using a not so great