RW
Russ Whaley
Thu, Jun 3, 2021 1:23 PM
Well, good news, bad news. I AM able to set breakpoints wherever I want in
Pharo (repo) code... and in many cases the breakpoint works and the
debugger pops up. However, I must have stumbled across (perhaps the only)
one that blows up when I run my app. See screenshot. To be clear, I've
had no issue extending Pharo repo classes (into my own packages). Besides
the bold red text stating the repos are missing in Iceberg :) this is the
only error I've come across. I have not spent a lot of time poking around
to see which classes allow breakpoints and which don't. Initially I feared
none of the breakpoints would work, but when I removed the breakpoint on
SpSingleSelectionMode - the next breakpoint (in Pharo repo) did fire and
brought up the debugger.
I've since worked around my problem (thanks Esteban!) and the breakpoint on
SpSingleSelectionMode is no longer required :)
Thanks!
Russ
On Thu, Jun 3, 2021 at 8:54 AM Joachim Tuchel jtuchel@objektfabrik.de
wrote:
David,
I don’t think the question is whether you need breakpoints or not. You
should be able to set breakpoints without these repositories. Maybe you
could give a few hints at what happens when you try…
Joachim
Am 03.06.2021 um 14:38 schrieb David Pennington <
Surely, one of the bases of OO development is to subclass and extend
existing classes? How can you code on the fly, as mentioned as one great
benefit of Smalltalk, if you can’t set break points? I have lost you here.
On 3 Jun 2021, at 08:39, Esteban Lorenzano estebanlm@netc.eu wrote:
I still do not understand why you need to repository at all.
you should not need it to do anything of what you are trying to do
(adding extensions and setting breakpoints).
Well, good news, bad news. I AM able to set breakpoints wherever I want in
Pharo (repo) code... and in many cases the breakpoint works and the
debugger pops up. However, I must have stumbled across (perhaps the only)
one that blows up when I run my app. See screenshot. To be clear, I've
had no issue extending Pharo repo classes (into my own packages). Besides
the bold red text stating the repos are missing in Iceberg :) this is the
only error I've come across. I have not spent a lot of time poking around
to see which classes allow breakpoints and which don't. Initially I feared
none of the breakpoints would work, but when I removed the breakpoint on
SpSingleSelectionMode - the next breakpoint (in Pharo repo) did fire and
brought up the debugger.
I've since worked around my problem (thanks Esteban!) and the breakpoint on
SpSingleSelectionMode is no longer required :)
Thanks!
Russ
On Thu, Jun 3, 2021 at 8:54 AM Joachim Tuchel <jtuchel@objektfabrik.de>
wrote:
> David,
>
> I don’t think the question is whether you need breakpoints or not. You
> should be able to set breakpoints without these repositories. Maybe you
> could give a few hints at what happens when you try…
>
> Joachim
>
> > Am 03.06.2021 um 14:38 schrieb David Pennington <
> david@totallyobjects.com>:
> >
> > Surely, one of the bases of OO development is to subclass and extend
> existing classes? How can you code on the fly, as mentioned as one great
> benefit of Smalltalk, if you can’t set break points? I have lost you here.
> > David
> >
> >> On 3 Jun 2021, at 08:39, Esteban Lorenzano <estebanlm@netc.eu> wrote:
> >>
> >> I still do not understand why you need to repository at all.
> >> you should not need it to do anything of what you are trying to do
> (adding extensions and setting breakpoints).
> >>
> >
>
--
Russ Whaley
whaley.russ@gmail.com
GC
Gabriel Cotelli
Thu, Jun 3, 2021 1:29 PM
Probably you put a breakpoint in code that is used by the debugger
infrastructure... you can use object-centric breakpoints for this use case
to break only on the presenter instance that you want to debug.
On Thu, Jun 3, 2021 at 10:24 AM Russ Whaley whaley.russ@gmail.com wrote:
Well, good news, bad news. I AM able to set breakpoints wherever I want
in Pharo (repo) code... and in many cases the breakpoint works and the
debugger pops up. However, I must have stumbled across (perhaps the only)
one that blows up when I run my app. See screenshot. To be clear, I've
had no issue extending Pharo repo classes (into my own packages). Besides
the bold red text stating the repos are missing in Iceberg :) this is the
only error I've come across. I have not spent a lot of time poking around
to see which classes allow breakpoints and which don't. Initially I feared
none of the breakpoints would work, but when I removed the breakpoint on
SpSingleSelectionMode - the next breakpoint (in Pharo repo) did fire and
brought up the debugger.
I've since worked around my problem (thanks Esteban!) and the breakpoint
on SpSingleSelectionMode is no longer required :)
Thanks!
Russ
On Thu, Jun 3, 2021 at 8:54 AM Joachim Tuchel jtuchel@objektfabrik.de
wrote:
David,
I don’t think the question is whether you need breakpoints or not. You
should be able to set breakpoints without these repositories. Maybe you
could give a few hints at what happens when you try…
Joachim
Am 03.06.2021 um 14:38 schrieb David Pennington <
Surely, one of the bases of OO development is to subclass and extend
existing classes? How can you code on the fly, as mentioned as one great
benefit of Smalltalk, if you can’t set break points? I have lost you here.
On 3 Jun 2021, at 08:39, Esteban Lorenzano estebanlm@netc.eu wrote:
I still do not understand why you need to repository at all.
you should not need it to do anything of what you are trying to do
(adding extensions and setting breakpoints).
Probably you put a breakpoint in code that is used by the debugger
infrastructure... you can use object-centric breakpoints for this use case
to break only on the presenter instance that you want to debug.
On Thu, Jun 3, 2021 at 10:24 AM Russ Whaley <whaley.russ@gmail.com> wrote:
> Well, good news, bad news. I AM able to set breakpoints wherever I want
> in Pharo (repo) code... and in many cases the breakpoint works and the
> debugger pops up. However, I must have stumbled across (perhaps the only)
> one that blows up when I run my app. See screenshot. To be clear, I've
> had no issue extending Pharo repo classes (into my own packages). Besides
> the bold red text stating the repos are missing in Iceberg :) this is the
> only error I've come across. I have not spent a lot of time poking around
> to see which classes allow breakpoints and which don't. Initially I feared
> none of the breakpoints would work, but when I removed the breakpoint on
> SpSingleSelectionMode - the next breakpoint (in Pharo repo) did fire and
> brought up the debugger.
>
> I've since worked around my problem (thanks Esteban!) and the breakpoint
> on SpSingleSelectionMode is no longer required :)
>
> Thanks!
> Russ
>
> On Thu, Jun 3, 2021 at 8:54 AM Joachim Tuchel <jtuchel@objektfabrik.de>
> wrote:
>
>> David,
>>
>> I don’t think the question is whether you need breakpoints or not. You
>> should be able to set breakpoints without these repositories. Maybe you
>> could give a few hints at what happens when you try…
>>
>> Joachim
>>
>> > Am 03.06.2021 um 14:38 schrieb David Pennington <
>> david@totallyobjects.com>:
>> >
>> > Surely, one of the bases of OO development is to subclass and extend
>> existing classes? How can you code on the fly, as mentioned as one great
>> benefit of Smalltalk, if you can’t set break points? I have lost you here.
>> > David
>> >
>> >> On 3 Jun 2021, at 08:39, Esteban Lorenzano <estebanlm@netc.eu> wrote:
>> >>
>> >> I still do not understand why you need to repository at all.
>> >> you should not need it to do anything of what you are trying to do
>> (adding extensions and setting breakpoints).
>> >>
>> >
>>
>
>
> --
> Russ Whaley
> whaley.russ@gmail.com
>
RW
Russ Whaley
Thu, Jun 3, 2021 1:32 PM
Yes, I figured I had done something taboo :)
On Thu, Jun 3, 2021 at 9:31 AM Gabriel Cotelli g.cotelli@gmail.com wrote:
Probably you put a breakpoint in code that is used by the debugger
infrastructure... you can use object-centric breakpoints for this use case
to break only on the presenter instance that you want to debug.
On Thu, Jun 3, 2021 at 10:24 AM Russ Whaley whaley.russ@gmail.com wrote:
Well, good news, bad news. I AM able to set breakpoints wherever I want
in Pharo (repo) code... and in many cases the breakpoint works and the
debugger pops up. However, I must have stumbled across (perhaps the only)
one that blows up when I run my app. See screenshot. To be clear, I've
had no issue extending Pharo repo classes (into my own packages). Besides
the bold red text stating the repos are missing in Iceberg :) this is the
only error I've come across. I have not spent a lot of time poking around
to see which classes allow breakpoints and which don't. Initially I feared
none of the breakpoints would work, but when I removed the breakpoint on
SpSingleSelectionMode - the next breakpoint (in Pharo repo) did fire and
brought up the debugger.
I've since worked around my problem (thanks Esteban!) and the breakpoint
on SpSingleSelectionMode is no longer required :)
Thanks!
Russ
On Thu, Jun 3, 2021 at 8:54 AM Joachim Tuchel jtuchel@objektfabrik.de
wrote:
David,
I don’t think the question is whether you need breakpoints or not. You
should be able to set breakpoints without these repositories. Maybe you
could give a few hints at what happens when you try…
Joachim
Am 03.06.2021 um 14:38 schrieb David Pennington <
Surely, one of the bases of OO development is to subclass and extend
existing classes? How can you code on the fly, as mentioned as one great
benefit of Smalltalk, if you can’t set break points? I have lost you here.
On 3 Jun 2021, at 08:39, Esteban Lorenzano estebanlm@netc.eu wrote:
I still do not understand why you need to repository at all.
you should not need it to do anything of what you are trying to do
(adding extensions and setting breakpoints).
Yes, I figured I had done something taboo :)
On Thu, Jun 3, 2021 at 9:31 AM Gabriel Cotelli <g.cotelli@gmail.com> wrote:
> Probably you put a breakpoint in code that is used by the debugger
> infrastructure... you can use object-centric breakpoints for this use case
> to break only on the presenter instance that you want to debug.
>
>
> On Thu, Jun 3, 2021 at 10:24 AM Russ Whaley <whaley.russ@gmail.com> wrote:
>
>> Well, good news, bad news. I AM able to set breakpoints wherever I want
>> in Pharo (repo) code... and in many cases the breakpoint works and the
>> debugger pops up. However, I must have stumbled across (perhaps the only)
>> one that blows up when I run my app. See screenshot. To be clear, I've
>> had no issue extending Pharo repo classes (into my own packages). Besides
>> the bold red text stating the repos are missing in Iceberg :) this is the
>> only error I've come across. I have not spent a lot of time poking around
>> to see which classes allow breakpoints and which don't. Initially I feared
>> none of the breakpoints would work, but when I removed the breakpoint on
>> SpSingleSelectionMode - the next breakpoint (in Pharo repo) did fire and
>> brought up the debugger.
>>
>> I've since worked around my problem (thanks Esteban!) and the breakpoint
>> on SpSingleSelectionMode is no longer required :)
>>
>> Thanks!
>> Russ
>>
>> On Thu, Jun 3, 2021 at 8:54 AM Joachim Tuchel <jtuchel@objektfabrik.de>
>> wrote:
>>
>>> David,
>>>
>>> I don’t think the question is whether you need breakpoints or not. You
>>> should be able to set breakpoints without these repositories. Maybe you
>>> could give a few hints at what happens when you try…
>>>
>>> Joachim
>>>
>>> > Am 03.06.2021 um 14:38 schrieb David Pennington <
>>> david@totallyobjects.com>:
>>> >
>>> > Surely, one of the bases of OO development is to subclass and extend
>>> existing classes? How can you code on the fly, as mentioned as one great
>>> benefit of Smalltalk, if you can’t set break points? I have lost you here.
>>> > David
>>> >
>>> >> On 3 Jun 2021, at 08:39, Esteban Lorenzano <estebanlm@netc.eu> wrote:
>>> >>
>>> >> I still do not understand why you need to repository at all.
>>> >> you should not need it to do anything of what you are trying to do
>>> (adding extensions and setting breakpoints).
>>> >>
>>> >
>>>
>>
>>
>> --
>> Russ Whaley
>> whaley.russ@gmail.com
>>
>
--
Russ Whaley
whaley.russ@gmail.com
SD
Stéphane Ducasse
Thu, Jun 3, 2021 7:34 PM
no just recursive and without correct exit :)
On 3 Jun 2021, at 15:32, Russ Whaley whaley.russ@gmail.com wrote:
Yes, I figured I had done something taboo :)
On Thu, Jun 3, 2021 at 9:31 AM Gabriel Cotelli <g.cotelli@gmail.com mailto:g.cotelli@gmail.com> wrote:
Probably you put a breakpoint in code that is used by the debugger infrastructure... you can use object-centric breakpoints for this use case to break only on the presenter instance that you want to debug.
On Thu, Jun 3, 2021 at 10:24 AM Russ Whaley <whaley.russ@gmail.com mailto:whaley.russ@gmail.com> wrote:
Well, good news, bad news. I AM able to set breakpoints wherever I want in Pharo (repo) code... and in many cases the breakpoint works and the debugger pops up. However, I must have stumbled across (perhaps the only) one that blows up when I run my app. See screenshot. To be clear, I've had no issue extending Pharo repo classes (into my own packages). Besides the bold red text stating the repos are missing in Iceberg :) this is the only error I've come across. I have not spent a lot of time poking around to see which classes allow breakpoints and which don't. Initially I feared none of the breakpoints would work, but when I removed the breakpoint on SpSingleSelectionMode - the next breakpoint (in Pharo repo) did fire and brought up the debugger.
I've since worked around my problem (thanks Esteban!) and the breakpoint on SpSingleSelectionMode is no longer required :)
Thanks!
Russ
On Thu, Jun 3, 2021 at 8:54 AM Joachim Tuchel <jtuchel@objektfabrik.de mailto:jtuchel@objektfabrik.de> wrote:
David,
I don’t think the question is whether you need breakpoints or not. You should be able to set breakpoints without these repositories. Maybe you could give a few hints at what happens when you try…
Joachim
Am 03.06.2021 um 14:38 schrieb David Pennington <david@totallyobjects.com mailto:david@totallyobjects.com>:
Surely, one of the bases of OO development is to subclass and extend existing classes? How can you code on the fly, as mentioned as one great benefit of Smalltalk, if you can’t set break points? I have lost you here.
David
On 3 Jun 2021, at 08:39, Esteban Lorenzano <estebanlm@netc.eu mailto:estebanlm@netc.eu> wrote:
I still do not understand why you need to repository at all.
you should not need it to do anything of what you are trying to do (adding extensions and setting breakpoints).
Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org
03 59 35 87 52
Assistant: Aurore Dalle
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley,
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France
no just recursive and without correct exit :)
> On 3 Jun 2021, at 15:32, Russ Whaley <whaley.russ@gmail.com> wrote:
>
> Yes, I figured I had done something taboo :)
>
> On Thu, Jun 3, 2021 at 9:31 AM Gabriel Cotelli <g.cotelli@gmail.com <mailto:g.cotelli@gmail.com>> wrote:
> Probably you put a breakpoint in code that is used by the debugger infrastructure... you can use object-centric breakpoints for this use case to break only on the presenter instance that you want to debug.
>
>
> On Thu, Jun 3, 2021 at 10:24 AM Russ Whaley <whaley.russ@gmail.com <mailto:whaley.russ@gmail.com>> wrote:
> Well, good news, bad news. I AM able to set breakpoints wherever I want in Pharo (repo) code... and in many cases the breakpoint works and the debugger pops up. However, I must have stumbled across (perhaps the only) one that blows up when I run my app. See screenshot. To be clear, I've had no issue extending Pharo repo classes (into my own packages). Besides the bold red text stating the repos are missing in Iceberg :) this is the only error I've come across. I have not spent a lot of time poking around to see which classes allow breakpoints and which don't. Initially I feared none of the breakpoints would work, but when I removed the breakpoint on SpSingleSelectionMode - the next breakpoint (in Pharo repo) did fire and brought up the debugger.
>
> I've since worked around my problem (thanks Esteban!) and the breakpoint on SpSingleSelectionMode is no longer required :)
>
> Thanks!
> Russ
>
> On Thu, Jun 3, 2021 at 8:54 AM Joachim Tuchel <jtuchel@objektfabrik.de <mailto:jtuchel@objektfabrik.de>> wrote:
> David,
>
> I don’t think the question is whether you need breakpoints or not. You should be able to set breakpoints without these repositories. Maybe you could give a few hints at what happens when you try…
>
> Joachim
>
> > Am 03.06.2021 um 14:38 schrieb David Pennington <david@totallyobjects.com <mailto:david@totallyobjects.com>>:
> >
> > Surely, one of the bases of OO development is to subclass and extend existing classes? How can you code on the fly, as mentioned as one great benefit of Smalltalk, if you can’t set break points? I have lost you here.
> > David
> >
> >> On 3 Jun 2021, at 08:39, Esteban Lorenzano <estebanlm@netc.eu <mailto:estebanlm@netc.eu>> wrote:
> >>
> >> I still do not understand why you need to repository at all.
> >> you should not need it to do anything of what you are trying to do (adding extensions and setting breakpoints).
> >>
> >
>
>
> --
> Russ Whaley
> whaley.russ@gmail.com <mailto:whaley.russ@gmail.com>
>
> --
> Russ Whaley
> whaley.russ@gmail.com <mailto:whaley.russ@gmail.com>
--------------------------------------------
Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org
03 59 35 87 52
Assistant: Aurore Dalle
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley,
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France
