same manner
Smalltalk environments do.
But then, F-Script is Smalltalk by any other name.
From: Dimitris Chloupis
Sent: Wednesday, November 1, 2017 7:28 PM
To: Any question about pharo is welcome; henry
Subject: Re: [Pharo-users] Pharo: Reinventing Smalltalk
Should pretty standard even for Java
: Wednesday, November 1, 2017 5:48 PM
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] Pharo: Reinventing Smalltalk
Well I rather not reply because I am a huge hater of multi window GUIs . Thank
god Pharo is not.
Seriously how on earth someone can find convenient multiple windows is
you rerun a java test case.
It's DOA.
- HH
> Original Message
> Subject: Re: [Pharo-users] Pharo: Reinventing Smalltalk
> Local Time: November 1, 2017 7:27 PM
> UTC Time: November 1, 2017 11:27 PM
> From: kilon.al...@gmail.com
> To: Any question about p
Should pretty standard even for Java using a debugger
I mean I have done this with Visual Studio and its debugger with C++. It
even allows you to inspect the machine code or see the memory in raw bits
formats. So I find it hard to believe that Eclipse cannot do that with Java.
There is even a fea
I am only familiar with Eclipse, not other Java development environments. In
comparison, what is lacking in the land of Java, which is so powerful in
Pharo/Squeak/Smalltalk is the ability to inspect the object resulting from some
highlighted code. As a developer, Smalltalk wins on inspectability
Well I rather not reply because I am a huge hater of multi window GUIs .
Thank god Pharo is not.
Seriously how on earth someone can find convenient multiple windows is
beyond my understanding . It was a terrible idea in 90s , it’s still a
terrible idea.
On Wed, 1 Nov 2017 at 23:05, horrido wrote:
