Re: [Pharo-dev] why sparta depends on Taskit?

Hi, > On Nov 7, 2016, at 8:51 AM, Esteban Lorenzano wrote: > > >> On 7 Nov 2016, at 07:41, Aliaksei Syrel wrote: >> >> Hi >> >> It is a library :) Even that there is an important difference between plugin >> and library we always refer to library in this thread. >> > I was thinking that bu

Re: [Pharo-dev] Instructions for Pharo 6 64bits

Hi Esteban. 2016-11-06 17:51 GMT+01:00 Esteban Lorenzano : > > height > "This method was automatically generated" > ^handle doubleAt: 17 > > height: anObject > "This method was automatically generated" > handle doubleAt: 17 put: anObject > > which of course does not work. > with my idea this will

Re: [Pharo-dev] [Pharo-users] About balkanisation

> On 7 Nov 2016, at 11:28, Dale Henrichs > wrote: > > > > On 11/7/16 4:52 AM, Esteban Lorenzano wrote: >> btw this is pharo-dev discussion, redirecting there. >> >> Esteban >> >>> On 7 Nov 2016, at 08:50, Esteban Lorenzano wrote: >>> >>> We are developing Iceberg… and I know is not enough

[Pharo-dev] Accessing Virtual machine internal?

Hi! Is there a way to get access to the VM internals? For example the size of the method cache and the number of JIT-compiled methods? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-dev] Accessing Virtual machine internal?

2016-11-07 13:37 GMT+01:00 Alexandre Bergel : > Hi! > > Is there a way to get access to the VM internals? For example the size of > the method cache and the number of JIT-compiled methods? > I don't know about the method cache siize, but for the number of JIT-Compiled methods is a primitive (a VM

Re: [Pharo-dev] Accessing Virtual machine internal?

Yes. Evaluate "Smalltalk vm parameterAt: 46" it should get you the machine code zone size. You can look into the comment in the VirtualMachine class or in VirtualMachine>>getParameters method comment to see what VM internal is available. On Nov 7, 2016 19:37, "Alexandre Bergel" wrote: > Hi! >

[Pharo-dev] Belgian Pharoers and coding day proposal

I would like to propose a coding day about Pharo. Here is the concept: people come over to my place(max 8) we do Pharo coding and have some nice food and drinks in the process. I wrote Belgian pharoers but that is not a limitation, just that it would be easier if you are near the place (Wavre).

Re: [Pharo-dev] Instructions for Pharo 6 64bits

2016-11-07 10:37 GMT+01:00 Denis Kudriashov : > NativeStructure >subclass : #SDL_Point >layout : StructureLayout >slots: { #x &=> #int. #y &=> #int} > ... > (I got example of Ronie definition from his paper https://hal.inria.fr/ > hal-01353884/document). > So all offsets logic will go

Re: [Pharo-dev] Belgian Pharoers and coding day proposal

If I can (calendar wise), I would be happy to join ! > On 7 Nov 2016, at 14:37, p...@highoctane.be wrote: > > I would like to propose a coding day about Pharo. > > Here is the concept: people come over to my place(max 8) we do Pharo coding > and have some nice food and drinks in the process. >

Re: [Pharo-dev] Instructions for Pharo 6 64bits

> On 7 Nov 2016, at 14:39, Nicolas Passerini wrote: > > > 2016-11-07 10:37 GMT+01:00 Denis Kudriashov >: > NativeStructure >subclass : #SDL_Point >layout : StructureLayout >slots: { #x &=> #int. #y &=> #int} > ... > (I got example of Ronie definition f

Re: [Pharo-dev] Instructions for Pharo 6 64bits

Well, maybe we can do it for Pharo 7. 2016-11-07 14:46 GMT+01:00 Esteban Lorenzano : > > On 7 Nov 2016, at 14:39, Nicolas Passerini wrote: > > > 2016-11-07 10:37 GMT+01:00 Denis Kudriashov : > >> NativeStructure >>subclass : #SDL_Point >>layout : StructureLayout >>slots: { #x &=> #in

Re: [Pharo-dev] Instructions for Pharo 6 64bits

> On 7 Nov 2016, at 14:53, Nicolas Passerini wrote: > > Well, maybe we can do it for Pharo 7. unless of course we find that doing it like this is incredibly easy and also we can do an “automigration tool” style the autodeprecation tool ;) Esteban > > 2016-11-07 14:46 GMT+01:00 Esteban Loren

Re: [Pharo-dev] [how about] Exceptions as first class objects *in Debugger*

+1 I had a prototype working at a certain point that send the exception to the debugger. I'll see if I can dig it up. It just involved chancing the API methods that open the debugger. Maybe a bit late for Pharo 6. On Sun, Nov 6, 2016 at 11:04 PM, Bernardo Ezequiel Contreras < vonbecm...@gmail.com

[Pharo-dev] [pharo-project/pharo-core] 4df786: 60284

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 4df786d8d29480e5cd2f631f3d3ea9f701e89cda https://github.com/pharo-project/pharo-core/commit/4df786d8d29480e5cd2f631f3d3ea9f701e89cda Author: Jenkins Build Server Date: 2016-11-07 (Mon, 07 Nov 2016

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60284 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] pillar latex and code listings

How are latex output of (named) code listings supposed to work /look ? I look at the pdf for the update PBE and the references to code example don't work (just show ??, it works for figures). The code in the code example isn't highlight and does't have a dark background (as it is in the html output

Re: [Pharo-dev] pillar latex and code listings

On 7 November 2016 at 23:03, Nicolai Hess wrote: > I look at the pdf for the update PBE and the references to code example > don't > work (just show ??, it works for figures). > Could be that the reference or label simply don't match… > The code in the code example isn't highlight and > does't