Workspace/Playground behavior change for unknown "bindings"?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Workspace/Playground behavior change for unknown "bindings"?

Holger Freyther
Hey,

I recently showed Pharo to a friend and one thing I like doing is to open a playground/workspace and then write and execute:


        Person new
                name: '...';
                age: 2342;
                yourself

In old versions of Pharo I would get a popup like "Person" not known and asking me if I want to create a class. In Pharo6.1 I did get an error. Was this intentional?


holger
Reply | Threaded
Open this post in threaded view
|

Re: Workspace/Playground behavior change for unknown "bindings"?

Ben Coman
On 7 February 2018 at 05:35, Holger Freyther <[hidden email]> wrote:

> Hey,
>
> I recently showed Pharo to a friend and one thing I like doing is to open a playground/workspace and then write and execute:
>
>
>         Person new
>                 name: '...';
>                 age: 2342;
>                 yourself
>
> In old versions of Pharo I would get a popup like "Person" not known and asking me if I want to create a class. In Pharo6.1 I did get an error. Was this intentional?

Intentional or not, thats a really simple quick demo that would be
good make it possible.

cheers -ben

Reply | Threaded
Open this post in threaded view
|

Re: Workspace/Playground behavior change for unknown "bindings"?

Marcus Denker-4
In reply to this post by Holger Freyther
Hello,

Yes, this is a bug… I have a fix and planned to merge it this week.

        https://pharo.fogbugz.com/f/cases/20254/Playground-should-ask-to-create-class-for-non-Existing-Globals

> On 6 Feb 2018, at 22:35, Holger Freyther <[hidden email]> wrote:
>
> Hey,
>
> I recently showed Pharo to a friend and one thing I like doing is to open a playground/workspace and then write and execute:
>
>
> Person new
> name: '...';
> age: 2342;
> yourself
>
> In old versions of Pharo I would get a popup like "Person" not known and asking me if I want to create a class. In Pharo6.1 I did get an error. Was this intentional?
>
>
> holger


Reply | Threaded
Open this post in threaded view
|

Re: Workspace/Playground behavior change for unknown "bindings"?

NorbertHartl
In reply to this post by Holger Freyther
Haha, same annoyance to me when I demonstrate.

Norbert


> Am 06.02.2018 um 22:35 schrieb Holger Freyther <[hidden email]>:
>
> Hey,
>
> I recently showed Pharo to a friend and one thing I like doing is to open a playground/workspace and then write and execute:
>
>
> Person new
> name: '...';
> age: 2342;
> yourself
>
> In old versions of Pharo I would get a popup like "Person" not known and asking me if I want to create a class. In Pharo6.1 I did get an error. Was this intentional?
>
>
> holger

Reply | Threaded
Open this post in threaded view
|

Re: Workspace/Playground behavior change for unknown "bindings"?

Marcus Denker-4
Ok, pull request for Pharo7:


we should add that to Pharo6, too (Slice is already in the inbox)

Marcus

On 7 Feb 2018, at 09:37, Norbert Hartl <[hidden email]> wrote:

Haha, same annoyance to me when I demonstrate.

Norbert


Am 06.02.2018 um 22:35 schrieb Holger Freyther <[hidden email]>:

Hey,

I recently showed Pharo to a friend and one thing I like doing is to open a playground/workspace and then write and execute:


Person new
name: '...';
age: 2342;
yourself

In old versions of Pharo I would get a popup like "Person" not known and asking me if I want to create a class. In Pharo6.1 I did get an error. Was this intentional?


holger


Reply | Threaded
Open this post in threaded view
|

Re: Workspace/Playground behavior change for unknown "bindings"?

Marcus Denker-4


On 7 Feb 2018, at 09:58, Marcus Denker <[hidden email]> wrote:

Ok, pull request for Pharo7:


we should add that to Pharo6, too (Slice is already in the inbox)


The idea is that this is the first step, we need to simplify the whole Requester-Scope story later.
(I was waiting to remove the old compiler *and* start to deprecate the old Api before doing that).

But it fixes the problem and is a first step.

Marcus

Reply | Threaded
Open this post in threaded view
|

Re: Workspace/Playground behavior change for unknown "bindings"?

Holger Freyther
In reply to this post by Marcus Denker-4


> On 7. Feb 2018, at 08:58, Marcus Denker <[hidden email]> wrote:
>
> Ok, pull request for Pharo7:
>
> https://github.com/pharo-project/pharo/pull/806
>
> we should add that to Pharo6, too (Slice is already in the inbox)
>

lovely! Thank you!