Branch: refs/heads/6.0
Home: https://github.com/pharo-project/pharo-core
Commit: 7faa3448b94469fdc68af5d97e75fbd206bfcea0
https://github.com/pharo-project/pharo-core/commit/7faa3448b94469fdc68af5d97e75fbd206bfcea0
Author: Jenkins Build Server
Date: 2017-02-09 (Thu, 09 Feb 2017
Branch: refs/tags/60379
Home: https://github.com/pharo-project/pharo-core
Hi All,
I've created the issue and associated slice:
https://pharo.fogbugz.com/f/cases/19680/DNU-bug-in-SLICE-18901
Thanks,
Alistair
On 8 February 2017 at 17:25, Nicolai Hess wrote:
>
>
> Am 08.02.2017 2:12 vorm. schrieb "Alistair Grant" :
>
> Hi Nicolai,
>
> On 7 February 2017 at 18:56, Nico
On Wed, Feb 8, 2017 at 8:24 PM, Hilaire wrote:
> Here my proposals. Please propose better alternative.
>
> Le 07/02/2017 à 21:02, Hilaire a écrit :
> > Full stack
>
> I really don't know what to write there.
>
Show the complete stack. By default the stacks shows a limited number of
stack frames.
Here my proposals. Please propose better alternative.
Le 07/02/2017 à 21:02, Hilaire a écrit :
> Full stack
I really don't know what to write there.
>
> Run to here
Execute methods up to the text cursor position and return debugger control.
> Where is?
Show the next method to be executed (s
Hi Steph
That is great news, thanks.
Note that I tried retrieving the document for Magritte via the following
screen:
The downloaded file has extension .pdf.txt, so doesn;t load / render
properly.
Can this please be changed to just .pdf? otherwise likely to trip up
newbies who need the help
Indeed. (We should one of these days improve the concurrent aspect of Pharo
but we should finish first the current open work)
On Wed, Feb 8, 2017 at 5:13 PM, Denis Kudriashov
wrote:
> Problem is related to RecursionStopper which not releases "stop method"
> while first debugger will be close or
Thanks!
On Wed, Feb 8, 2017 at 6:05 PM, Stephane Ducasse
wrote:
> Hi
>
> https://ci.inria.fr/pharo-contribution/view/Books/
> I realised that jenkins dropped the connection to the github repositories
> of the books and that they were not updated.
> You can find my current evening occupation: Le
Hi
https://ci.inria.fr/pharo-contribution/view/Books/
I realised that jenkins dropped the connection to the github repositories
of the books and that they were not updated.
You can find my current evening occupation: Learning OOP with Pharo :)
I fixed some problems in UnifiedFFI and clean a bit b
Problem is related to RecursionStopper which not releases "stop method"
while first debugger will be close or step over.
Also this "stop method" is Halt>>once which could be mistake.
Probably RecoursionStopper should be process specific variable and not
global registry.
2017-02-08 17:04 GMT+01:00
That's strange.
I found that if you step over halt then you are able to halt on next call.
Anyway it needs to be fixed
2017-02-08 16:37 GMT+01:00 Ben Coman :
>
> This has bugged me a few times recently, so I've produced a demo.
> Define...
>
> Object subclass: #AA
> instanceVariableNames: ''
>
2017-02-08 16:37 GMT+01:00 Ben Coman :
>
> This has bugged me a few times recently, so I've produced a demo.
> Define...
>
> Object subclass: #AA
> instanceVariableNames: ''
> classVariableNames: ''
> package: ''
>
> AA>>test
> self haltOnce.
> self inform: 'I got here'.
>
> then in playgr
This has bugged me a few times recently, so I've produced a demo.
Define...
Object subclass: #AA
instanceVariableNames: ''
classVariableNames: ''
package: ''
AA>>test
self haltOnce.
self inform: 'I got here'.
then in playground evaluate
Halt resetOnce. "i.e. World > Debugging > Ena
looks good to me.
On Tue, Feb 7, 2017 at 8:40 AM, Sven Van Caekenberghe wrote:
>
> > On 7 Feb 2017, at 08:05, Stephane Ducasse
> wrote:
> >
> > Sven I do not get
> >
> > Step over the highlighted message, i.e. do not follow the sent message,
> taking debugger control after the method invoked re
Hi Stefan,
Thanks for your insight.
On Wed, Feb 8, 2017 at 4:47 PM, Stefan Marr wrote:
> Hi Ben:
>
>> On 8 Feb 2017, at 08:01, Ben Coman wrote:
>>
>> Just a very brief thought, to wonder being a Language Server Protocol client
>> might be a path to polygot programming in Pharo.
>> Or if providin
Yes, the protocol first step is about "Documents"
What do you think would be the best thing for "Document" besides
"ChangeSet"?
We can have
$root/packagename/classname/[class|instance]/protocol/method.st mapping
with method as document but there would be quite a lot.
$root/packagename/classname
Hi Ben:
> On 8 Feb 2017, at 08:01, Ben Coman wrote:
>
> Just a very brief thought, to wonder being a Language Server Protocol client
> might be a path to polygot programming in Pharo.
> Or if providing a LSP server might be a bridge-head
> for Pharo to be integrated into larger projects.
>
>
17 matches
Mail list logo