Re: [Pharo-dev] Pillar configuration bug ?

2016-06-06 Thread Yann Dubois
I add two groups : - parser : To load the Pillar parser - parser tests : To testing the parser Yann 2016-06-04 11:45 GMT+02:00 Cyril Ferlicot D. : > Le 03/06/2016 14:51, Esteban Lorenzano a écrit : > > Without the parser you can’t do anything so I would expect the parser to > be a core part. >

Re: [Pharo-dev] STON toJsonString produces broken JSON

2016-06-06 Thread Sven Van Caekenberghe
I just committed: === Name: STON-Core-SvenVanCaekenberghe.76 Author: SvenVanCaekenberghe Time: 6 June 2016, 10:34:01.602265 am UUID: 71eeced4-4b1a-4648-90fa-c89efa709ba6 Ancestors: STON-Core-SvenVanCaekenberghe.75 When in JSON mode, STONWriter should also signal an STONWriterError when an Associ

Re: [Pharo-dev] Do we want AST-Debugger?

2016-06-06 Thread Denis Kudriashov
Hi Eliot. 2016-06-06 1:13 GMT+02:00 Eliot Miranda : > That's simply not true. In fact the amount known of the VM in both the > bytecode debugger and the AST debugger is the same; both use VM primitives > that aren't specified at the image level. > > Both the AST interpreter and the bytecode inte

Re: [Pharo-dev] Do we want AST-Debugger?

2016-06-06 Thread Denis Kudriashov
2016-06-06 10:45 GMT+02:00 Denis Kudriashov : > >> But seriously, the system is based on bytecode, and that bytecode is >> pretty straightforward and easy to learn. Why not put in the effort of >> learning it? >> >> Criticizing something in ignorance is not wise IMO. >> > > I just put this method

Re: [Pharo-dev] Do we want AST-Debugger?

2016-06-06 Thread Denis Kudriashov
2016-06-06 10:45 GMT+02:00 Denis Kudriashov : > One area where you'll find the AST debugger worse is in performance. The > bytecode debugger uses perform: to execute at full speed when possible (it > does interpret when doing step into or through, but not when doing over). > In fact this part of

Re: [Pharo-dev] STON toJsonString produces broken JSON

2016-06-06 Thread Peter Uhnak
On Mon, Jun 06, 2016 at 10:36:02AM +0200, Sven Van Caekenberghe wrote: > I just committed: > > === > Name: STON-Core-SvenVanCaekenberghe.76 > Author: SvenVanCaekenberghe > Time: 6 June 2016, 10:34:01.602265 am > UUID: 71eeced4-4b1a-4648-90fa-c89efa709ba6 > Ancestors: STON-Core-SvenVanCaekenberghe.

[Pharo-dev] atomicity of non-local returns

2016-06-06 Thread Ben Coman
I understand generally that an inlined #ifTrue is atomic. For example, here after the primitive returns, no interruption can occur before the #ensure is invoked... self primitiveWaitAcquire ifTrue: [mutuallyExclusiveBlock ensure: [self release]]. But I want to know whether a non-

Re: [Pharo-dev] atomicity of non-local returns

2016-06-06 Thread Clément Bera
Hi Ben, Firstly be careful because atomic usually means that the thread cannot be interrupted by a concurrent native thread, so an atomic operation has to be guaranteed at processor level. Assuming that by atomic you mean that the operation's process cannot be preempted by another green thread, y

[Pharo-dev] [Ann] ObjectStatistics

2016-06-06 Thread Denis Kudriashov
Hello. I just publish new tool ObjectStatistics to analyze objects set. I first created it to analyze network communication during remote debugging. And then I realize how general it could be. Now it is ready to use package. It could be good foundation to improve and simplify our profiler tools.

Re: [Pharo-dev] [Ann] ObjectStatistics

2016-06-06 Thread Denis Kudriashov
And you can load it by Gofer it smalltalkhubUser: 'Pharo' project: 'ObjectStatistics'; configuration; loadStable And play with examples on ObjectStatistics class side 2016-06-06 16:53 GMT+02:00 Denis Kudriashov : > Hello. > > I just publish new tool ObjectStatistics to analyze objects set. > I

Re: [Pharo-dev] atomicity of non-local returns

2016-06-06 Thread Ben Coman
On Mon, Jun 6, 2016 at 9:34 PM, Clément Bera wrote: > Hi Ben, > > Firstly be careful because atomic usually means that the thread cannot be > interrupted by a concurrent native thread, so an atomic operation has to be > guaranteed at processor level. > > Assuming that by atomic you mean that the o

Re: [Pharo-dev] atomicity of non-local returns

2016-06-06 Thread Clément Bera
Yeah anyway the non local return happens after the ensure: send, so nothing to worry about. In your analysis, you need to see that the #returnTop bytecode means NLR in a block but method return in a method. Even if it looks the same, in one case the #returnTop belongs to a block closure bytecode,

Re: [Pharo-dev] [Ann] ObjectStatistics

2016-06-06 Thread p...@highoctane.be
Nice thing! On Mon, Jun 6, 2016 at 4:56 PM, Denis Kudriashov wrote: > And you can load it by > > Gofer it smalltalkhubUser: 'Pharo' project: 'ObjectStatistics'; > configuration; loadStable > > And play with examples on ObjectStatistics class side > > 2016-06-06 16:53 GMT+02:00 Denis Kudriashov :

[Pharo-dev] Privacy sendDiagnosticsAndUsageData should be ternary, not binary

2016-06-06 Thread Peter Uhnak
Hi, Privacy>>sendDiagnosticsAndUsageData should be ternary, not binary. Because right now if I refuse sending the data I will be asked again every single time. So the proper behavior (imho) should be: ask Privacy for the setting… if the setting is not defined, then show a popup. If the setting

Re: [Pharo-dev] atomicity of non-local returns

2016-06-06 Thread Ben Coman
On Tue, Jun 7, 2016 at 2:39 AM, Clément Bera wrote: > Yeah anyway the non local return happens after the ensure: send, so nothing > to worry about. > > In your analysis, you need to see that the #returnTop bytecode means NLR in > a block but method return in a method. Even if it looks the same, in

Re: [Pharo-dev] atomicity of non-local returns

2016-06-06 Thread Clément Bera
On Tue, Jun 7, 2016 at 1:55 AM, Ben Coman wrote: > On Tue, Jun 7, 2016 at 2:39 AM, Clément Bera > wrote: > > Yeah anyway the non local return happens after the ensure: send, so > nothing > > to worry about. > > > > In your analysis, you need to see that the #returnTop bytecode means NLR > in > >

Re: [Pharo-dev] Playground and text evaluation printing result default.

2016-06-06 Thread stepharo
Le 5/6/16 à 23:00, Tudor Girba a écrit : Hi Stef, The quotes appear only when you add the result in the playground. No need to explain I'm not idiot and I know it. The typical use case for this is to keep track of several results. No need to explain I'm not idiot and I know it. In this si