Re: [Pharo-dev] Grease ?

Le 25/5/16 à 21:45, Nicolai Hess a écrit : There is a bug report 18324 about spelling mistakes in Pharo 5.0 I fixed them for Pharo 5, but some errors reported are for classes named GRNonPortableMessageRule,

[Pharo-dev] Grease ?

There is a bug report 18324 about spelling mistakes in Pharo 5.0 I fixed them for Pharo 5, but some errors reported are for classes named GRNonPortableMessageRule, GRUsesCurlyBraceArraysRule... I guess these packages are from

[Pharo-dev] [pharo-project/pharo-core] 0e6398: 50759

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

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

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

Re: [Pharo-dev] Screenshot of Pharo 64 bits

> On 25 May 2016, at 14:46, David T. Lewis wrote: > > On Wed, May 25, 2016 at 11:27:04AM +0200, Cl??ment Bera wrote: >> There are quite some progress on the plugin work. >> >> Eliot made x64 FFI working a couple months ago. >> >> Nicolas Cellier have already been looking

Re: [Pharo-dev] Screenshot of Pharo 64 bits

On Wed, May 25, 2016 at 11:27:04AM +0200, Cl??ment Bera wrote: > There are quite some progress on the plugin work. > > Eliot made x64 FFI working a couple months ago. > > Nicolas Cellier have already been looking for Number plugins for a while. > > Many Slang compilation bugs related to 32-64

[Pharo-dev] [pharo-project/pharo-core] 971dfd: 50758

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

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

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

[Pharo-dev] [UFFI] Call a function where argument type is char ** (argv)

Hello, I have written a R bridge in Pharo and I would like to migrate it from NativeBoost to UFFI. Most of the changes are easy to do but I am stuck to a double pointer problem. I have to call the function: int Rf_initEmbeddedR(int argc, char ** argv). I know how to give the int but the char **

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

Hi. Look at AST-Interpreter project which includes AST-Debugger http://smalltalkhub.com/#!/~Pharo/AST-Interpreter. Code is so simple comparing to "bytecode simulation" approach of current debugger. AST debugger are independent from bytecode set. It just visit AST-nodes to simulate code execution.

Re: [Pharo-dev] strange Zinc JPEG bug

Here is the fix: === Name: Zinc-HTTP-SvenVanCaekenberghe.450 Author: SvenVanCaekenberghe Time: 25 May 2016, 11:02:23.445172 am UUID: 2785db13-be7c-4ec1-86ce-ca8b4d58bae1 Ancestors: Zinc-HTTP-SvenVanCaekenberghe.449 Re-implement ZnEasy class >> #get[Png|Jpeg|Gif] so that ImageReadWriter decides

Re: [Pharo-dev] strange Zinc JPEG bug

> On 25 May 2016, at 08:42, stepharo wrote: > > > > Le 24/5/16 à 19:50, Henrik Nergaard a écrit : >> Not sure where to report zinc bugs… fogzbugz? or is it a separate project? >> Any bug found in the standard image regardless of project should be reported >> on fogbugz, no?

[Pharo-dev] [pharo-project/pharo-core] 4009b9: 60035

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

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

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

Re: [Pharo-dev] about ensureCreateFile

We were discussing it when I was in Lille. >From my side the conclusion was… do whatever you want with it, as long as there is a (new) method that raises an error when the parent does not exist. On Wed, May 25, 2016 at 8:40 AM, stepharo wrote: > I would like to move on on

Re: [Pharo-dev] [pharo-project/pharo-core] edfbef: 60034

I did it already. 2016-05-25 10:26 GMT+02:00 stepharo : > because I was in the process of integrating it. Now I will close it. > > Le 25/5/16 à 09:10, Pavel Krivanek a écrit : > > 18302 icons -> icons iconNamed: (part 1) > >

Re: [Pharo-dev] [pharo-project/pharo-core] edfbef: 60034

because I was in the process of integrating it. Now I will close it. Le 25/5/16 à 09:10, Pavel Krivanek a écrit : 18302 icons -> icons iconNamed: (part 1) https://pharo.fogbugz.com/f/cases/18302 This issue is not closed. Why? -- Pavel 2016-05-25 8:57 GMT+02:00 GitHub

Re: [Pharo-dev] [pharo-project/pharo-core] edfbef: 60034

18302 icons -> icons iconNamed: (part 1) https://pharo.fogbugz.com/f/cases/18302 This issue is not closed. Why? -- Pavel 2016-05-25 8:57 GMT+02:00 GitHub : > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit:

Re: [Pharo-dev] slice/merge conflict with package AST-FFI-Pharo50Compatibility

2016-05-25 8:47 GMT+02:00 stepharo : > hi nicolai > > > let me know when this is ready to integrate. > > We are trying to purge the queue but sometimes I end up redoing the > changes in fast mode. > Thanks, fix for 17696 should work now (monkey is checking). > > Stef > > Le

[Pharo-dev] [pharo-project/pharo-core] edfbef: 60034

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

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

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

Re: [Pharo-dev] slice/merge conflict with package AST-FFI-Pharo50Compatibility

hi nicolai let me know when this is ready to integrate. We are trying to purge the queue but sometimes I end up redoing the changes in fast mode. Stef Le 25/5/16 à 00:06, Nicolai Hess a écrit : 2016-05-24 23:51 GMT+02:00 Henrik Nergaard

Re: [Pharo-dev] strange Zinc JPEG bug

Le 24/5/16 à 19:50, Henrik Nergaard a écrit : Not sure where to report zinc bugs… fogzbugz? or is it a separate project? Any bug found in the standard image regardless of project should be reported on fogbugz, no? Yes I imgaine that there is zinc project there else we should create one.

[Pharo-dev] about ensureCreateFile

I would like to move on on this one: https://pharo.fogbugz.com/f/cases/18084/FileReference-EnsureCreateFile I'm in favor of the change. But I'm all ears. Stef