[Pharo-dev] Functional callbacks on all Cog platforms

Hi All, just wanted to report that as of Alien-eem.35 and https://github.com/OpenSmalltalk/vm/commit/da3fafdec9444754af104e0ed9f613f6eb1888d9 we now have functional callbacks on all x86 platforms, ARM32 platforms and x86_64 platforms. There's a simple example Alien class>>exampleCqsort that

Re: [Pharo-dev] question

> On Jun 22, 2016, at 8:25 AM, Clément Bera wrote: > > It's a special case added a couple year ago to figure out why a primitive > fail. That's right. It was an exception to the rule in VisualWorks and its convenience is so strong I brought it over. But the

Re: [Pharo-dev] AthensCairoSurface not getting garbage collected

Thanks for this report! I also experience crashes, that are hard to reproduce. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 22, 2016, at 1:18 PM, J.F. Rick

Re: [Pharo-dev] AthensCairoSurface not getting garbage collected

Here's some more information on this: When I was having this issue, Pharo was pretty unstable. It would crash regularly when using AthensCairoSurface. It would also sometimes have weird visual artifacts. I'm not sure what these were but it almost looked like the bits were shifted so that rgb

Re: [Pharo-dev] question

It's a special case added a couple year ago to figure out why a primitive fail. It's a special temporary variable that holds an error code. The special object array defines a list of error code that the VM can use to explain to the programmer why the primitive failed, which are currently symbols.

Re: [Pharo-dev] senders seems broken

broken, or a deprecation warning 2016-06-22 16:14 GMT+02:00 stepharo : > Ok > > I'm in the train so I will not try to download it :) > > The finder is broken. We cannot use the dropdown. > > Do you know if it was fixed too. > > > Setf > > > Le 22/6/16 à 16:02, Marcus Denker a

Re: [Pharo-dev] question

> On 22 Jun 2016, at 15:59, stepharo wrote: > > Hi > > I want to explain where ec is coming. > > I thought that the arguments of pragmas could only be literal and when I see > ec it looks like a variable set by the VM > > > newMethod: numberOfBytes header: headerWord >

Re: [Pharo-dev] shit + double click on a category :)

Cool! I didn't know about it :) On Wed, Jun 22, 2016 at 10:54 AM, stepharo wrote: > We should call a method rename and class rename refactoring for classes > and methods and it will be gorgeous :) > > yes it is shift :) > > > Setf > > Le 22/6/16 à 11:50, Denis Kudriashov a

Re: [Pharo-dev] senders seems broken

Ok I'm in the train so I will not try to download it :) The finder is broken. We cannot use the dropdown. Do you know if it was fixed too. Setf Le 22/6/16 à 16:02, Marcus Denker a écrit : There where bugs but they should be fixed in the latest version. (in 60105 it works for me again).

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

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

[Pharo-dev] [pharo-project/pharo-core] fbf352: 60107

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: fbf3521210b17541b348788746be6210e0d3fb40 https://github.com/pharo-project/pharo-core/commit/fbf3521210b17541b348788746be6210e0d3fb40 Author: Jenkins Build Server Date:

Re: [Pharo-dev] senders seems broken

There where bugs but they should be fixed in the latest version. (in 60105 it works for me again). > On 22 Jun 2016, at 15:53, stepharo wrote: > > Hi marcus > > can you browse senders? Because I cannot anymore. > > Stef > >

[Pharo-dev] question

Hi I want to explain where ec is coming. I thought that the arguments of pragmas could only be literal and when I see ec it looks like a variable set by the VM newMethod: numberOfBytes header: headerWord "Primitive. Answer an instance of me. The number of literals (and other

Re: [Pharo-dev] NonInteractiveUIManager vs. Epicea

Le 22/6/16 à 14:35, Martin Dias a écrit : On Wed, Jun 22, 2016 at 4:31 AM, stepharo > wrote: Le 22/6/16 à 00:23, Holger Freyther a écrit : Hi, would fogbugz be the better place for reports like this? It looks like

Re: [Pharo-dev] shit + double click on a category :)

We should call a method rename and class rename refactoring for classes and methods and it will be gorgeous :) yes it is shift :) Setf Le 22/6/16 à 11:50, Denis Kudriashov a écrit : Really nice. And I found that double click on method opens new browser on it. 2016-06-22 11:44 GMT+02:00

[Pharo-dev] senders seems broken

Hi marcus can you browse senders? Because I cannot anymore. Stef

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

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

[Pharo-dev] [pharo-project/pharo-core] cd235a: 60106

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: cd235aa9f5569e172c7499b3157559b35c4bcb31 https://github.com/pharo-project/pharo-core/commit/cd235aa9f5569e172c7499b3157559b35c4bcb31 Author: Jenkins Build Server Date:

Re: [Pharo-dev] shit + double click on a category :)

Really nice. And I found that double click on method opens new browser on it. 2016-06-22 11:44 GMT+02:00 stepharo : > Hi guys > > alain showed me that click + double click on a category is really nice to > rename a category. > > May be you knew it but this is nice. > > > Stef >

Re: [Pharo-dev] shit + double click on a category :)

It’s neither “shit” nor “click” but thanks for the pointer :D (spoiler: it’s “shift”) > On 22 Jun 2016, at 11:44, stepharo wrote: > > Hi guys > > alain showed me that click + double click on a category is really nice to > rename a category. > > May be you knew it but this

Re: [Pharo-dev] shit + double click on a category :)

Could shortcut reminder capture this? > On 22 Jun 2016, at 11:44, stepharo wrote: > > Hi guys > > alain showed me that click + double click on a category is really nice to > rename a category. > > May be you knew it but this is nice. > > > Stef > >

[Pharo-dev] shit + double click on a category :)

Hi guys alain showed me that click + double click on a category is really nice to rename a category. May be you knew it but this is nice. Stef

Re: [Pharo-dev] [pharo-project/pharo-core] 6ece95: 60104

Yes.. some problems with the script that clean the stack… Side effect of a fix (which is wrong) is that 105 now has no UI process. We are rebuilding it now with the cleanup script disabled. > On 22 Jun 2016, at 10:15, Nicolai Hess wrote: > > I don't know what change is

[Pharo-dev] [pharo-project/pharo-core] c15659: 60105

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: c156598f552379c776301dbdecc650a36688f513 https://github.com/pharo-project/pharo-core/commit/c156598f552379c776301dbdecc650a36688f513 Author: Jenkins Build Server Date:

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

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

[Pharo-dev] Fwd: [pharo-project/pharo-core] 6ece95: 60104

I don't know what change is responsible, but Pharo 60104 as two ui-processes (this causes strange rendering artefacts) -- Forwarded message -- From: GitHub Date: 2016-06-22 10:03 GMT+02:00 Subject: [Pharo-dev] [pharo-project/pharo-core] 6ece95: 60104 To:

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

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