Re: [Pharo-dev] .filetree file?

Le 13/01/2016 01:48, Mariano Martinez Peck a écrit : Hi Alex, I was wondering the same just minutes ago. I wonder if GitFileTree could do this for us? Well, it looks like a bug. It normally writes and commit it by itself, but it seems that, in certain conditions, it gets written and committed

Re: [Pharo-dev] [Ann] ReadWriteLock

These two read together provide a balanced view. ReaderWriterLock vs Monitor http://www.interact-sw.co.uk/iangblog/2004/04/26/rwlockvsmonitor When to use the ReaderWriterLock https://www.interact-sw.co.uk/iangblog/2004/05/12/rwlock cheers -ben On Wed, Jan 13, 2016 at 6:27 AM, Jan Vrany wrote:

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

> Le 12/1/16 17:58, Denis Kudriashov a écrit : > > Hi > > UFFI reminds me UFO which can be translated like Unified Foreign Objects. > And objects outside image look really like unidentified flying objects. It's > just address, blob of bytes and they fly outside smalltalk world > And it has some re

Re: [Pharo-dev] .filetree file?

Hi Alex, I was wondering the same just minutes ago. I wonder if GitFileTree could do this for us? On Sun, Jul 5, 2015 at 7:03 PM, Alexandre Bergel wrote: > Ok, thanks! > > Alexandre > > > > On Jul 6, 2015, at 12:02 AM, Sven Van Caekenberghe wrote: > > > > > >> On 05 Jul 2015, at 23:57, Alexa

Re: [Pharo-dev] [Ann] ReadWriteLock

Hi. I am going to bed now. Do you look at wikipedia link? 12 янв. 2016 г. 11:29 PM пользователь "Jan Vrany" написал: > Hi Denis, all, > > I'm sorry for asking basic questions, but... > > I thought of this a little and I failed to see the advantage > of using ReadWriteLock over monitor / mutex. Wh

Re: [Pharo-dev] [Pharo-users] [ann] gtdebugger in pharo 5.0

no, I’m quite sure they are bugs :) I also believe the other tools do not have accept/cancel visible (they are in contextual menus), so maybe they should be there. Esteban > On 12 Jan 2016, at 23:24, Nicolai Hess wrote: > > > > 2016-01-08 11:24 GMT+01:00 Tudor Girba

Re: [Pharo-dev] [Ann] ReadWriteLock

Hi Denis, all,  I'm sorry for asking basic questions, but... I thought of this a little and I failed to see the advantage  of using ReadWriteLock over monitor / mutex. What's the goal of ReadWriteLock? I mean - when should I use it rather than  monitor / mutex? What practical advantage would it h

Re: [Pharo-dev] [Pharo-users] [ann] gtdebugger in pharo 5.0

2016-01-08 11:24 GMT+01:00 Tudor Girba : > Hi, > > We are about to integrate in Pharo a new member of the Glamorous Toolkit: > the GTDebugger. As this is a significant change that might affect your > workflow, here is some background information to help you deal with the > change. > > First, you s

[Pharo-dev] [pharo-project/pharo-core] c496dd: 50524

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: c496dd7263104cfd1ba78ed2098194f9ac989b2e https://github.com/pharo-project/pharo-core/commit/c496dd7263104cfd1ba78ed2098194f9ac989b2e Author: Jenkins Build Server Date: 2016-01-12 (Tue, 12 Jan 2016

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

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

Re: [Pharo-dev] How to get launcher launching Spur images?

On 12-01-16 15:23, Ben Coman wrote: On Tue, Jan 12, 2016 at 10:03 PM, stepharo wrote: I loaded the stable version in Pharo 50 and I saw that it does not have the Spur special Folder. So I loaded the latest version of the packages from the repo and I could not run the launcher anymore. So could

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

2016-01-12 16:49 GMT-03:00 stepharo : > > > Le 12/1/16 17:58, Denis Kudriashov a écrit : > > Hi > > UFFI reminds me UFO which can be translated like Unified Foreign Objects. > And it has some relation to Alien name. > But maybe it is too much funny name > > > Quite cool :) > +1 UFFI is concise

Re: [Pharo-dev] Bad layoutFrame>>#hash

Hi david I rad the wikipedia page you mention and this looks a bit obvious to me. I knew this. now it does not really help fixing the problem you mention. Stef Le 11/1/16 10:09, David Allouche a écrit : Since it's not obvious why xor-ing is a bad way to produce hash, here is a link that giv

Re: [Pharo-dev] Bad layoutFrame>>#hash

Ok but be concrete. What will be the solution for this particular case? Stef Le 11/1/16 22:30, Nicolas Cellier a écrit : Yep, a must read if you want to improve the hash methods. 2016-01-11 10:09 GMT+01:00 Sven Van Caekenberghe >: David, > On 11 Jan 2016, at 10:

Re: [Pharo-dev] Bad layoutFrame>>#hash

You see K. Beck in his book smalltalk best pratices promotes this form. So can you propose a better solution so that we learn? Stef Le 11/1/16 10:09, David Allouche a écrit : Since it's not obvious why xor-ing is a bad way to produce hash, here is a link that gives some background https://en.

Re: [Pharo-dev] ifError: implementation is bad

+^111 We should make a list. Some that should be easy: - Delay should be splitted why? - Chronology should be splitted One more complicated: - InstructionClient and InstructionStream should be splitted And then, we should also review the API of basic objects Object methods size

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

Ah I forgot the name UFFI is also used by the Common Lisp http://www.cliki.net/UFFI On Tue, Jan 12, 2016 at 9:50 PM stepharo wrote: > > > Le 12/1/16 17:58, Denis Kudriashov a écrit : > > Hi > > UFFI reminds me UFO which can be translated like Unified Foreign Objects. > And it has some relation

Re: [Pharo-dev] How to get launcher launching Spur images?

ok I will retry. Le 12/1/16 15:23, Ben Coman a écrit : On Tue, Jan 12, 2016 at 10:03 PM, stepharo wrote: I loaded the stable version in Pharo 50 and I saw that it does not have the Spur special Folder. So I loaded the latest version of the packages from the repo and I could not run the launche

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

Le 12/1/16 17:58, Denis Kudriashov a écrit : Hi UFFI reminds me UFO which can be translated like Unified Foreign Objects. And it has some relation to Alien name. But maybe it is too much funny name Quite cool :) Stef 2016-01-12 16:55 GMT+01:00 Esteban Lorenzano

[Pharo-dev] Job offer

Begin forwarded message: From: Georg Heeg Subject: [Esug-list] Looking for Smalltalkers Date: 12 Jan 2016 17:57:27 GMT+1 To: ESUG Mailing list A customer of ours is looking for two Smalltalkers starting not later as July 1st, 2016, unlimited work contracts. Please contact me for details G

Re: [Pharo-dev] Redirect bug in Zinc in the recent Pharo 5 images

> On 12 Jan 2016, at 15:05, Sven Van Caekenberghe wrote: > > Hi Monty, > > Thanks for reporting this issue. > > The problem is that Zn requests > http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd using Host: > www.oasis-open.org:80 (so with an explicit port) and apparently this server

Re: [Pharo-dev] happy lessons from recent talks

Tudor Girba-2 wrote > Hi, > > I just wanted to share with you a bit of a different perspective on what > we do around here. > > Over the past half a year I gave several talks to some 1k technical people > at industrial events like ArchConf, NDC Oslo and several others. The tour > will continue th

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

Why not "Pharo FFI" ? since it will be the official FFI of Pharo. I also like like lighthouse references like "LightSpeed" , "LightForce" , "LightWave" , "Lighting", "LightHouse" etc. On Tue, Jan 12, 2016 at 5:57 PM Esteban Lorenzano wrote: > Hi, > > People has pointed (and they are right) that

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

Esteban Lorenzano wrote: > People has pointed (and they are right) that the name of the new FFI > front-end is misleading. "People" means more than just a single person (me). Glad that I'm not the only one who lamented ;) > So yesterday I was talking with Stef and we think UnifiedFFI (or UFFI,

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

UniFFIed ? On 12 January 2016 at 17:40, Max Leske wrote: > In order of preference: > > 1. UnifiedFFI > 2. FFI-Unified (suggests that there may be multiple FFI implementations) > 3. UFFI (not clear to me that this is an FFI) > > Cheers, > Max > > > On 12 Jan 2016, at 16:55, Esteban Lorenzano wro

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

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

[Pharo-dev] [pharo-project/pharo-core] 980d4d: 50523

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 980d4dfa986e3db8067a7ffc1f4a7b43f6454f91 https://github.com/pharo-project/pharo-core/commit/980d4dfa986e3db8067a7ffc1f4a7b43f6454f91 Author: Jenkins Build Server Date: 2016-01-12 (Tue, 12 Jan 2016

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

2016-01-12 18:08 GMT+01:00 Denis Kudriashov : > > 2016-01-12 17:58 GMT+01:00 Denis Kudriashov : > >> UFFI reminds me UFO which can be translated like Unified Foreign Objects. >> And it has some relation to Alien name. > > > And objects outside image look really like unidentified flying objects. >

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

2016-01-12 17:58 GMT+01:00 Denis Kudriashov : > UFFI reminds me UFO which can be translated like Unified Foreign Objects. > And it has some relation to Alien name. And objects outside image look really like unidentified flying objects. It's just address, blob of bytes and they fly outside smallt

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

Hi UFFI reminds me UFO which can be translated like Unified Foreign Objects. And it has some relation to Alien name. But maybe it is too much funny name 2016-01-12 16:55 GMT+01:00 Esteban Lorenzano : > Hi, > > People has pointed (and they are right) that the name of the new FFI > front-end is mi

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

In order of preference: 1. UnifiedFFI 2. FFI-Unified (suggests that there may be multiple FFI implementations) 3. UFFI (not clear to me that this is an FFI) Cheers, Max > On 12 Jan 2016, at 16:55, Esteban Lorenzano wrote: > > Hi, > > People has pointed (and they are right) that the name of th

[Pharo-dev] I will rename FFI-NB to UnifiedFFI

Hi, People has pointed (and they are right) that the name of the new FFI front-end is misleading. So yesterday I was talking with Stef and we think UnifiedFFI (or UFFI, for short) is a better name… and to keep packages prox. to regular FFI I was thinking on rename FFI-NB packages to FFI-Unifie

Re: [Pharo-dev] [Moose-dev] Re: [Survey] Forking Operating System Proces in Pharo

Done ! I am very excited about this project. There a lot of gui apps that offer an interface via command line and I am interested into running Pharo on multiple cores. On Tue, 12 Jan 2016 at 17:21, Mariano Martinez Peck wrote: > Dear all, > > This is a simple reminder in case someone missed it. >

Re: [Pharo-dev] [Survey] Forking Operating System Proces in Pharo

Dear all, This is a simple reminder in case someone missed it. I also wanted to thank everybody that already took the time for filling it! Very much appreciated. On Sat, Jan 2, 2016 at 10:44 AM, Mariano Martinez Peck < marianop...@gmail.com> wrote: > Dear all, > > As I mentioned in the thread

Re: [Pharo-dev] How to get launcher launching Spur images?

On Tue, Jan 12, 2016 at 10:03 PM, stepharo wrote: > I loaded the stable version in Pharo 50 and I saw that it does not have the > Spur special Folder. > So I loaded the latest version of the packages from the repo and I could not > run the launcher anymore. > > So could you tell me how you did it?

Re: [Pharo-dev] Morphic Migrations gotchas, was Re: Better class comment version2

2016-01-12 11:02 GMT+01:00 David Allouche : > I wonder whether it would be worth reversing this change, to remove an > unnecessary incompatibility with other dialects. > > But maybe there is no development activity outside of Pharo, that would > justify making any effort to maintain compatibility.

Re: [Pharo-dev] Morphic Migrations gotchas, was Re: Better class comment version2

On Tue, Jan 12, 2016 at 6:02 PM, David Allouche wrote: > I wonder whether it would be worth reversing this change, to remove an > unnecessary incompatibility with other dialects. Of course we should not introduce *unnecessary* incompatibilities, but its be hard to judge the subtle dampening effec

Re: [Pharo-dev] How to get launcher launching Spur images?

I loaded the stable version in Pharo 50 and I saw that it does not have the Spur special Folder. So I loaded the latest version of the packages from the repo and I could not run the launcher anymore. So could you tell me how you did it? Stef Le 11/1/16 16:48, stepharo a écrit : Ok I will do

Re: [Pharo-dev] Test Runner: "Run Coverage" fails or hangs when multithreading is used in test.

> Maybe it should only lock the threads that were _not_ started by the > “test thread”? I’m not even sure that is possible, > just suggesting things. > Have a look at Niall Ross' XProc Patterns. They do the same by - AFAIK - intercepting process creation and checking whether the creating process

Re: [Pharo-dev] Pharo50 spur works on CentOS?

Ah yes, that is better, thanks! > On 12 Jan 2016, at 11:54, Blondeau Vincent > wrote: > > Agree. > I open a bug: > https://pharo.fogbugz.com/f/cases/17378/Improve-command-line-handler-documentation-and-help > that improve the doc. > I propose: > Usage: > [--no-preferences|--preference-file=]

Re: [Pharo-dev] Pharo50 spur works on CentOS?

Agree. I open a bug: https://pharo.fogbugz.com/f/cases/17378/Improve-command-line-handler-documentation-and-help that improve the doc. I propose: Usage: [--no-preferences|--preference-file=][--help|--list|--copyright|--version|--no-quit| ] --help print this help message --

Re: [Pharo-dev] Pharo50 spur works on CentOS?

No, I don't think so, it has a function. Some people like to configure Pharo images so that they have a running server inside them. In that case, starting your app is a simple as starting the image, but you would probably need the --no-quit to prevent it from exiting immediately. (I personally

Re: [Pharo-dev] Test Runner: "Run Coverage" fails or hangs when multithreading is used in test.

Haha, don’t worry. You don’t have to shut up, in fact I thank you for replying. I don’t know exactly how it has been implemented, I had a look see and it seems to be like this: It seems to collect all methods that will be checked for coverage, and then instantiate a wrapper around each one, and

Re: [Pharo-dev] Pharo50 spur works on CentOS?

So --no-quit should be removed from the default line handler? Vincent > -Message d'origine- > De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de > Esteban Lorenzano > Envoyé : mardi 12 janvier 2016 11:18 > À : Pharo Development List > Objet : Re: [Pharo-dev] Pharo50 s

Re: [Pharo-dev] Pharo50 spur works on CentOS?

But you cannot use it as a general command. If you use a subcommand (most likely) then you do not have it unless the subcommand defines it. Esteban > On 12 Jan 2016, at 11:12, Blondeau Vincent > wrote: > > > >> -Message d'origine- >> De : Pharo-dev [mailto:pharo-dev-boun...@lists.p

Re: [Pharo-dev] Pharo50 spur works on CentOS?

> -Message d'origine- > De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de > Sven Van Caekenberghe > Envoyé : mardi 12 janvier 2016 10:57 > À : Pharo Development List > Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS? > > > > On 12 Jan 2016, at 10:50, Esteban Lor

Re: [Pharo-dev] Test Runner: "Run Coverage" fails or hangs when multithreading is used in test.

The coverage seems to be implemented by 'locking' the current execution thread exclusively, which would mean no other threads can run, at all. So code depending on multi threading, like client/server code, like HTTP, cannot work. Yes that seems to be a limitation, but an understandable one. I a

Re: [Pharo-dev] Test Runner: "Run Coverage" fails or hangs when multithreading is used in test.

"can NOT check"*, in the first sentence. > On Jan 12, 2016, at 11:05 AM, Skip Lentz wrote: > > You mean as in it can check the coverage effected by the code running in the > other thread? > Or is this not what you mean? > > Well I mean, at least it can show the coverage done by what was run in

Re: [Pharo-dev] Test Runner: "Run Coverage" fails or hangs when multithreading is used in test.

You mean as in it can check the coverage effected by the code running in the other thread? Or is this not what you mean? Well I mean, at least it can show the coverage done by what was run in the same thread.. And it will at least not hang or fail. > On Jan 12, 2016, at 10:59 AM, Sven Van Caeke

Re: [Pharo-dev] Morphic Migrations gotchas, was Re: Better class comment version2

I wonder whether it would be worth reversing this change, to remove an unnecessary incompatibility with other dialects. But maybe there is no development activity outside of Pharo, that would justify making any effort to maintain compatibility. I do not know. Practicality beats purity, if clean

Re: [Pharo-dev] Test Runner: "Run Coverage" fails or hangs when multithreading is used in test.

I never used that, but it seems coverage can only deal with single threaded code, which sounds logical. No ? > On 12 Jan 2016, at 10:53, Skip Lentz wrote: > > Hi, > > When I want to run the coverage of for example Zinc’s Client and Server tests, > it will either hang (in the case of Zinc’s tes

Re: [Pharo-dev] Pharo50 spur works on CentOS?

> On 12 Jan 2016, at 10:50, Esteban Lorenzano wrote: > > > >> On 12 Jan 2016, at 10:34, Sven Van Caekenberghe wrote: >> >> >>> On 12 Jan 2016, at 10:28, Blondeau Vincent >>> wrote: >>> >>> Indeed, it works. Thanks! >>> >>> But the command line usage is not clear : >>> ./pharo Pharo.imag

[Pharo-dev] Test Runner: "Run Coverage" fails or hangs when multithreading is used in test.

Hi, When I want to run the coverage of for example Zinc’s Client and Server tests, it will either hang (in the case of Zinc’s test cases) or fail because the coverage uses BlockClosure>>valueUnpreemptively for running the tests. The relevant method is TestRunner>>collectCoverageFor:. So when a t

Re: [Pharo-dev] Pharo50 spur works on CentOS?

> On 12 Jan 2016, at 10:34, Sven Van Caekenberghe wrote: > > >> On 12 Jan 2016, at 10:28, Blondeau Vincent >> wrote: >> >> Indeed, it works. Thanks! >> >> But the command line usage is not clear : >> ./pharo Pharo.image >> Usage: [--no-preferences|--preference-file=][] [--help] >> [--copy

Re: [Pharo-dev] Pharo50 spur works on CentOS?

> On 12 Jan 2016, at 10:28, Blondeau Vincent > wrote: > > Indeed, it works. Thanks! > > But the command line usage is not clear : > ./pharo Pharo.image > Usage: [--no-preferences|--preference-file=][] [--help] > [--copyright] [--version] [--list] [ --no-quit ] > > Maybe, it can be : > Usage

Re: [Pharo-dev] Pharo50 spur works on CentOS?

No, because --no-quit option is an option of eval subcommand (is not present for all) What can be improved is the explanation on how to use the command line, for example: -list list subcommands subcommand --help show subcommand help > On 12 Jan 2016, at 10:28, Blondeau Vincent > wrote: >

Re: [Pharo-dev] Pharo50 spur works on CentOS?

> On 12 Jan 2016, at 10:28, Blondeau Vincent > wrote: > > Indeed, it works. Thanks! > > But the command line usage is not clear : > ./pharo Pharo.image > Usage: [--no-preferences|--preference-file=][] [--help] > [--copyright] [--version] [--list] [ --no-quit ] > > Maybe, it can be : > Usage:

Re: [Pharo-dev] Pharo50 spur works on CentOS?

Indeed, it works. Thanks! But the command line usage is not clear : ./pharo Pharo.image Usage: [--no-preferences|--preference-file=][] [--help] [--copyright] [--version] [--list] [ --no-quit ] Maybe, it can be : Usage: [--no-preferences|--preference-file=][] [--help] [--copyright] [--version] [

[Pharo-dev] Shutting down persona.org in November 2016

Hi, both pharo.org and pillarhub.pharocloud.com rely on persona.org for authentication. This service will disappear. --- Begin Message --- Hi Everyone, When the Mozilla Identity team transitioned Persona to community ownership, we committed resources to operational and security support through

Re: [Pharo-dev] Atomic commits

Dimitris Chloupis writes: > Most coders that use git rely on a git client of some sort, if you dont > like guis and prefer emacs, there is also magit that i hear is very good. totally agree, Magit is awesome. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go

Re: [Pharo-dev] Understanding Spotter?

> Am 12.01.2016 um 09:23 schrieb Sven Van Caekenberghe : > > >> On 12 Jan 2016, at 09:19, Christophe Demarey >> wrote: >> >> Hi Doru, >> >> Definitely, it would be a great addition. >> I really like spotter but I still need to open some browser or playground to >> search implementors or sen

Re: [Pharo-dev] Understanding Spotter?

> On 12 Jan 2016, at 09:19, Christophe Demarey > wrote: > > Hi Doru, > > Definitely, it would be a great addition. > I really like spotter but I still need to open some browser or playground to > search implementors or senders. > This feature + a way to perform exact match will avoid to open

Re: [Pharo-dev] Understanding Spotter?

Hi Doru, Definitely, it would be a great addition. I really like spotter but I still need to open some browser or playground to search implementors or senders. This feature + a way to perform exact match will avoid to open extra windows and to loose time. Keep pushing, Christophe Le 11 janv.