For what it's worth, here's a moderately thorough examination of several
different Smalltalk systems.
Let A = astc, D = Dolphin, G = GNU Smalltalk, Q = Squeak,
S = ANSI standard, T = Strongtalk, V = VisualWorks, X = ST/X
#asString
ADGPQST!X Character => String with: self
ADGPQSTVX String =>
Also, regarding keeping your images under control, if you haven't downloaded
and started using Pharo Launcher, you should! It's a fabulous tool...
http://pharo.org/download
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Hi,
Your document is definitely out of date! The current version of PBE for
version 5, 6, and 7 can be found here:
https://github.com/SquareBracketAssociates/UpdatedPharoByExample/releases
If you're using Pharo 8 or 9, you'll want the updated version, PBE8, which
can be found here:
https://gith
Hi all,
I’ve been lurking so far, but I must add my voice here and agree with Richard.
The malleability of Smalltalk tempts people into implementing #asString, #name,
and similar semantically ambiguous method names. Like Richard, I regretted
every single time I (or someone else on my team befor
On May 11, 2020 2:19:49 PM PDT, Richard O'Keefe wrote:
>I was saying that I expected #($a $b $c) asString ==> 'abc'.
Over the years, I found myself being opposed to the idea that all objects can
sensibly have an #asString implementation. When it's been done, it ultimately
caused more problem
I was saying that I expected #($a $b $c) asString ==> 'abc'.
If you want something that can be read back, that's what #storeString is for,
On Tue, 12 May 2020 at 01:28, Stéphane Ducasse
wrote:
>
>
>
> On 5 May 2020, at 16:16, Richard O'Keefe wrote:
>
> By the way, while playing with this problem
--- Begin Message ---
I read the section in 2018-09-29-UPDATEDPHAROBYEXAMPLE:
"Monticello packages” just after Figure 3-27
I have a smalltalkhub account and created a repository:
MCHttpRepository
location: 'http://smalltalkhub.com/mc/MichaelKentBurns/FredsLunch/main'
user: ''
> By the way, while playing with this problem, I ran into a moderately
> painful issue.
>
> There is a reason that Smalltalk has both #printString (to get a
> printable representation of an object) and #asString (to convert a
> sequence to another kind of sequence with the same elements.) If I
>
In the past we added metadata to manifest.
And the compedium could take advantage of that.
We will have to work on it (end of the month).
S
> On 4 May 2020, at 01:33, Torsten Bergmann wrote:
>
> Yes - I was developing on P9 and never tried it in Pharo 8. But I checked now
> - seems to work
