Re: [Pharo-dev] summary of "float & fraction equality bug"

2017-11-10 23:04 GMT+01:00 Florin Mateoc : > On 11/10/2017 4:42 PM, Florin Mateoc wrote: > > On 11/10/2017 4:18 PM, Nicolas Cellier wrote: > > > > 2017-11-10 20:58 GMT+01:00 Martin McClure : > >> On 11/10/2017 11:33 AM, raffaello.giulie...@lifeware.ch

Re: [Pharo-dev] summary of "float & fraction equality bug"

2017-11-10 22:42 GMT+01:00 Florin Mateoc : > On 11/10/2017 4:18 PM, Nicolas Cellier wrote: > > > > 2017-11-10 20:58 GMT+01:00 Martin McClure : > >> On 11/10/2017 11:33 AM, raffaello.giulie...@lifeware.ch wrote: >> >>> Doing only Fraction->Float

Re: [Pharo-dev] summary of "float & fraction equality bug"

On 11/10/2017 4:42 PM, Florin Mateoc wrote: > On 11/10/2017 4:18 PM, Nicolas Cellier wrote: >> >> >> 2017-11-10 20:58 GMT+01:00 Martin McClure > >: >> >> On 11/10/2017 11:33 AM, raffaello.giulie...@lifeware.ch >>

Re: [Pharo-dev] summary of "float & fraction equality bug"

On 11/10/2017 4:18 PM, Nicolas Cellier wrote: > > > 2017-11-10 20:58 GMT+01:00 Martin McClure >: > > On 11/10/2017 11:33 AM, raffaello.giulie...@lifeware.ch > wrote: > > Doing only

Re: [Pharo-dev] feenk log

Hi Sean, Why not `anElement simulateClick`? Good question :) We indeed evaluated a possibility to have (BlElement >> #simulateClick) but then decided to make BlSpace class to be responsible for that. First we should realise that when we simulate a click we do literally simulate user's action

Re: [Pharo-dev] Alternative window manager

Hi Thomas, On 10 November 2017 at 11:46, Thomas Dupriez wrote: > Hello, > > Does an alternative window manager for pharo exist? > > For some reasons I always end up with a tangled mess of windows when using > the default one. My biggest gripe is that new

Re: [Pharo-dev] summary of "float & fraction equality bug"

2017-11-10 20:58 GMT+01:00 Martin McClure : > On 11/10/2017 11:33 AM, raffaello.giulie...@lifeware.ch wrote: > >> Doing only Fraction->Float conversions in mixed mode won't preserve = as >> an equivalence relation and won't enable a consistent ordering with <=, >> which

[Pharo-dev] [Pharo 7.0-dev] Build #284: 20671-Extend-system-dependencies-tests-on-whole-image

There is a new Pharo build available! The status of the build #284 was: SUCCESS. The Pull Request #464 was integrated: "20671-Extend-system-dependencies-tests-on-whole-image" Pull request url: https://github.com/pharo-project/pharo/pull/464 Issue Url:

Re: [Pharo-dev] feenk log

Tudor Girba-2 wrote > - support for programatic testing of bloc mouse events: > https://twitter.com/feenkcom/status/925672206763511808 Why not `anElement simulateClick`? - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] summary of "float & fraction equality bug"

On 11/10/2017 11:33 AM, raffaello.giulie...@lifeware.ch wrote: Doing only Fraction->Float conversions in mixed mode won't preserve = as an equivalence relation and won't enable a consistent ordering with <=, which probably most Smalltalkers consider important and enjoyable properties. Good

[Pharo-dev] [Pharo 7.0-dev] Build #283: 20670-unused-var-in-generateDefaultFileOutResultsName

There is a new Pharo build available! The status of the build #283 was: SUCCESS. The Pull Request #465 was integrated: "20670-unused-var-in-generateDefaultFileOutResultsName" Pull request url: https://github.com/pharo-project/pharo/pull/465 Issue Url:

Re: [Pharo-dev] summary of "float & fraction equality bug"

On 2017-11-10 19:45, Martin McClure wrote: > On 11/10/2017 03:59 AM, raffaello.giulie...@lifeware.ch wrote: >> I would like to summarize my perspective of what emerged from the >> discussions in the "float & fraction equality bug" trail. >> >> The topic is all about mixed operations when both

Re: [Pharo-dev] summary of "float & fraction equality bug"

> On Nov 10, 2017, at 7:45 PM, Martin McClure wrote: > > On 11/10/2017 03:59 AM, raffaello.giulie...@lifeware.ch wrote: >> I would like to summarize my perspective of what emerged from the >> discussions in the "float & fraction equality bug" trail. >> >> The topic is

[Pharo-dev] feenk log

Hi, Over the past couple of weeks Alex worked on stabilizing a first beta01 version for Pharo 6.1: https://twitter.com/feenkcom/status/929031849879461889 This is available as a beta01 tag in the pharo61 branch here: https://github.com/pharo-graphics/Bloc/tree/beta01 The main readme was updated

Re: [Pharo-dev] summary of "float & fraction equality bug"

On 11/10/2017 03:59 AM, raffaello.giulie...@lifeware.ch wrote: I would like to summarize my perspective of what emerged from the discussions in the "float & fraction equality bug" trail. The topic is all about mixed operations when both Fractions and Floats are involved in the mix and can be

Re: [Pharo-dev] Encoding method source code in Tonel

none of them, I’m sorry :) I think we can do a lot better with just a bit of effort. Esteban > On 10 Nov 2017, at 15:26, Stephane Ducasse wrote: > > I would prefer the last one. > Regularity over exception. > Now the parser should just be good :) > > Stef > > On Fri,

Re: [Pharo-dev] Encoding method source code in Tonel

I would prefer the last one. Regularity over exception. Now the parser should just be good :) Stef On Fri, Nov 10, 2017 at 7:20 PM, Sven Van Caekenberghe wrote: > > >> On 10 Nov 2017, at 19:12, Stephane Ducasse wrote: >> >> Hi sven >> >> Do you have an

Re: [Pharo-dev] Encoding method source code in Tonel

> On 10 Nov 2017, at 19:12, Stephane Ducasse wrote: > > Hi sven > > Do you have an example because I do not understand your doubling. Sure, Bla { bla:bla } [ self isFoo ifTrue: [ #foo ] ifFalse: [ [ "block" #bar ]] ] would have to become Bla { bla:bla } [ self

Re: [Pharo-dev] Encoding method source code in Tonel

Hi sven Do you have an example because I do not understand your doubling. stef On Fri, Nov 10, 2017 at 11:40 AM, Sven Van Caekenberghe wrote: > Hi, > > Right now, TonelParser>>#methodBody looks a bit dangerous (too complex), and > Nicolas already found some breaking cases as

Re: [Pharo-dev] Encoding method source code in Tonel

Hi Nico, I have a fix for both cases you provided. now, I need to refactor it because is ugly how I solve it :) right now this is super agnostic: the only thing we ensure is to count correctly the brackets to be sure we have a complete method. All the cases you mention it are possible ways

Re: [Pharo-dev] Encoding method source code in Tonel

> On 10 Nov 2017, at 13:05, Denis Kudriashov wrote: > > 2017-11-10 17:03 GMT+01:00 Denis Kudriashov >: > > 2017-11-10 16:30 GMT+01:00 Martin McClure >: > Tonel

Re: [Pharo-dev] 6.1 Iceberg - how is this supposed to work?

Yes, trying to install your libclang. Pharo is brand new download of whatever is on the website - 6.1-64 bit version (yes I know its not tested - I was going to test it). OSX Sierra. I have Xcode and all that goes with it installed (my day job is IoT projects with accompanying iPhone apps and

Re: [Pharo-dev] Encoding method source code in Tonel

2017-11-10 17:03 GMT+01:00 Denis Kudriashov : > > 2017-11-10 16:30 GMT+01:00 Martin McClure : >> >> Tonel is intended to be, I believe: >> * For Smalltalk primarily (although there are other languages) >> * Be for any Smalltalk dialect (although the

Re: [Pharo-dev] Encoding method source code in Tonel

2017-11-10 16:30 GMT+01:00 Martin McClure : > > Tonel is intended to be, I believe: > * For Smalltalk primarily (although there are other languages) > * Be for any Smalltalk dialect (although the first implementation is for > Pharo, it is being ported to GemStone, and we

[Pharo-dev] [Pharo 7.0-dev] Build #282: 20668-add-breakpoints-menu-to-Nautilus-segment-icons

There is a new Pharo build available! The status of the build #282 was: SUCCESS. The Pull Request #463 was integrated: "20668-add-breakpoints-menu-to-Nautilus-segment-icons" Pull request url: https://github.com/pharo-project/pharo/pull/463 Issue Url:

Re: [Pharo-dev] Encoding method source code in Tonel

On 11/10/2017 07:11 AM, Nicolas Cellier wrote: The first goals are:  - we should prefer a syntax agnostic format for two reasons     * not insulting the future and supporting alternate syntax extensions (compilerClass)     * making the parsing both robust and efficient (not necessary to use a

Re: [Pharo-dev] Encoding method source code in Tonel

2017-11-10 16:21 GMT+01:00 Sven Van Caekenberghe : > > > > On 10 Nov 2017, at 16:11, Nicolas Cellier gmail.com> wrote: > > > > There are other possibilities: if we don't want to change the methodBody > at all, then let's change the opening/closing

Re: [Pharo-dev] Encoding method source code in Tonel

> On 10 Nov 2017, at 16:11, Nicolas Cellier > wrote: > > There are other possibilities: if we don't want to change the methodBody at > all, then let's change the opening/closing sequence > > - at write, choose a closing sequence that has no exact match in

Re: [Pharo-dev] Encoding method source code in Tonel

On 11/10/2017 07:10 AM, Esteban Lorenzano wrote: Well… I’m working on make it more robust :) but in general, I disagree with all solutions style “force some character to appear in one place”. I prefer to rely in a good (better) parsing than to force such kind of conventions that are also very

Re: [Pharo-dev] Encoding method source code in Tonel

2017-11-10 12:08 GMT+01:00 Sven Van Caekenberghe : > > > > On 10 Nov 2017, at 11:59, Nicolas Cellier gmail.com> wrote: > > > > My proposition was to force methodBody closing to be on first column, > > and disambiguate potential method conflicts by

Re: [Pharo-dev] Encoding method source code in Tonel

Well… I’m working on make it more robust :) but in general, I disagree with all solutions style “force some character to appear in one place”. I prefer to rely in a good (better) parsing than to force such kind of conventions that are also very easy to break (as soon as people can modify things

[Pharo-dev] [Pharo 7.0-dev] Build #281: 20055-immediateByteSubclass-is-deadcoe

There is a new Pharo build available! The status of the build #281 was: SUCCESS. The Pull Request #462 was integrated: "20055-immediateByteSubclass-is-deadcoe" Pull request url: https://github.com/pharo-project/pharo/pull/462 Issue Url: https://pharo.fogbugz.com/f/cases/20055 Build Url:

Re: [Pharo-dev] summary of "float & fraction equality bug"

On 11/10/2017 9:39 AM, Florin Mateoc wrote: > I think we should also mention that the literal 0.1 is not the number in base > ten that we all learned in school, despite > both using base 10 for printing and despite both being printed the same way - > this is the crux of the problem. > > But

Re: [Pharo-dev] summary of "float & fraction equality bug"

I think we should also mention that the literal 0.1 is not the number in base ten that we all learned in school, despite both using base 10 for printing and despite both being printed the same way - this is the crux of the problem. But there is such a number in the system, called ScaledDecimal,

[Pharo-dev] [Pharo 7.0-dev] Build #280: 17654-SpecPreDebugWindow-and-subclasses-relies-on-doesNotUnderstand-delegation-to-find-the-stackPane

There is a new Pharo build available! The status of the build #280 was: SUCCESS. The Pull Request #461 was integrated: "17654-SpecPreDebugWindow-and-subclasses-relies-on-doesNotUnderstand-delegation-to-find-the-stackPane" Pull request url: https://github.com/pharo-project/pharo/pull/461

Re: [Pharo-dev] Metacello we need automated conflict resolution between Baselines and Configurations

On 11/10/17 1:14 AM, Peter Uhnák wrote: Hi Dale, I am aware of locking, but that requires I know all the recursive dependencies so I can lock them before loading the project itself. I can do that locally (and I've done it in the past), but I cannot easily force that upon users. This also

Re: [Pharo-dev] Catalog problem

Thx Sven. That led me to check the url which worked fine. http://catalog.pharo.org/catalog/json Then I had to close and restart the image and its was working fine. So now nothing to examine :(. Minor side issue that I'm ignoring for now (just reporting for completeness)... putting a halt in

Re: [Pharo-dev] Tonel line end convention

Does iceberg respect git line ending settings? https://help.github.com/articles/dealing-with-line-endings/ On Fri, Nov 10, 2017 at 2:02 PM, Gabriel Cotelli wrote: > Can we add an empty line at the end of every tonel file? GitHub diff tools > work better that way and for the

Re: [Pharo-dev] Catalog problem

Try closing Pharo and opening it again... this is imho due to slow Inria servers and I've encountered it many times. On Fri, Nov 10, 2017 at 1:57 PM, Sven Van Caekenberghe wrote: > Check CatalogProvider. It should download the catalog from the cloud and > cache it locally. If not

Re: [Pharo-dev] Tonel line end convention

Can we add an empty line at the end of every tonel file? GitHub diff tools work better that way and for the rest it shouldn't matter. On Fri, Nov 10, 2017 at 8:26 AM, Esteban Lorenzano wrote: > > > > On 10 Nov 2017, at 07:25, Sven Van Caekenberghe wrote: > >

Re: [Pharo-dev] Catalog problem

Check CatalogProvider. It should download the catalog from the cloud and cache it locally. If not you can work from there on to see what is wrong. > On 10 Nov 2017, at 13:32, Ben Coman wrote: > > Today I downloaded Pharo and found Catalog to be empty. >

[Pharo-dev] Catalog problem

Today I downloaded Pharo and found Catalog to be empty. http://files.pharo.org/platform/Pharo6.1-64-linux.zip cheers -ben

Re: [Pharo-dev] summary of "float & fraction equality bug"

Thanks indeed for the summary. I like this. Doru > On Nov 10, 2017, at 12:59 PM, raffaello.giulie...@lifeware.ch wrote: > > I would like to summarize my perspective of what emerged from the > discussions in the "float & fraction equality bug" trail. > > The topic is all about mixed operations

Re: [Pharo-dev] summary of "float & fraction equality bug"

Good summary. I must add to comparison and operations, I’d add encoding, where ASN.1 Reals MUST convert to Float before encoding with mantissa, exponent, etc. Here is another Fraction -> Float conversion. As well as ScaledDecimal -> Float conversion. Sent from ProtonMail Mobile On Fri, Nov

Re: [Pharo-dev] summary of "float & fraction equality bug"

I would like to summarize my perspective of what emerged from the discussions in the "float & fraction equality bug" trail. The topic is all about mixed operations when both Fractions and Floats are involved in the mix and can be restated as the question of whether it is better to automagically

Re: [Pharo-dev] Tonel line end convention

> On 10 Nov 2017, at 12:26, Esteban Lorenzano wrote: > > > >> On 10 Nov 2017, at 07:25, Sven Van Caekenberghe wrote: >> >> Hi, >> >> I am wondering if the current approach regarding the Tonel line end >> convention is a good idea. >> >>

Re: [Pharo-dev] Tonel line end convention

> On 10 Nov 2017, at 07:25, Sven Van Caekenberghe wrote: > > Hi, > > I am wondering if the current approach regarding the Tonel line end > convention is a good idea. > > TonelWriter>>#newLine > ^ OSPlatform current lineEnding > > Although it is no problem to write Pharo code

Re: [Pharo-dev] Encoding method source code in Tonel

> On 10 Nov 2017, at 11:59, Nicolas Cellier > wrote: > > My proposition was to force methodBody closing to be on first column, > and disambiguate potential method conflicts by forcing a more transparent > white space. > > Maybe we can force the white

Re: [Pharo-dev] Encoding method source code in Tonel

My proposition was to force methodBody closing to be on first column, and disambiguate potential method conflicts by forcing a more transparent white space. Maybe we can force the white space only on conflicting lines that would begin with a ]. Most methods are indented (and even formatted) so

Re: [Pharo-dev] Encoding method source code in Tonel

> On 10 Nov 2017, at 11:49, Henrik Sperre Johansen > wrote: > > Can a line with a single ] ever at the "right" indentation level? > Forcing autoformat at commit is a bit heavy hand, but maybe inserting a tab > (or 2,3,4 spaces?) would be an ok workaround that

[Pharo-dev] [Pharo 7.0-dev] Build #279: 20363-ThemeIconsdownloadTo-has-an-argument-which-is-never-referenced-in-code

There is a new Pharo build available! The status of the build #279 was: SUCCESS. The Pull Request #453 was integrated: "20363-ThemeIconsdownloadTo-has-an-argument-which-is-never-referenced-in-code" Pull request url: https://github.com/pharo-project/pharo/pull/453 Issue Url:

Re: [Pharo-dev] Encoding method source code in Tonel

Can a line with a single ] ever at the "right" indentation level? Forcing autoformat at commit is a bit heavy hand, but maybe inserting a tab (or 2,3,4 spaces?) would be an ok workaround that doesn't require special decoding when loading the code? Cheers, Henry -- Sent from:

[Pharo-dev] Alternative window manager

Hello, Does an alternative window manager for pharo exist? For some reasons I always end up with a tangled mess of windows when using the default one. My biggest gripe is that new windows tend to open on top of other windows, blocking the view even if there is still empty space elsewhere.

[Pharo-dev] Encoding method source code in Tonel

Hi, Right now, TonelParser>>#methodBody looks a bit dangerous (too complex), and Nicolas already found some breaking cases as well a one possible solution. I was thinking a bit along the same lines, so here is a proposal. Overall I think we should keep the current readability of Tonel as much

[Pharo-dev] Tonel line end convention

Hi, I am wondering if the current approach regarding the Tonel line end convention is a good idea. TonelWriter>>#newLine ^ OSPlatform current lineEnding Although it is no problem to write Pharo code that transparently deals with (accepts) any line end convention, not specifying a fixed line

Re: [Pharo-dev] 6.1 Iceberg - how is this supposed to work?

I would need a way to reproduce this. pharo version? (6.1?) vm version? operating system? project you try to install? (I guess is libclang) anything I should know about your environment? (image is clean/new? are you behind a proxy? whatever that can help) Esteban > On 10 Nov 2017, at 00:08,

Re: [Pharo-dev] Metacello we need automated conflict resolution between Baselines and Configurations

Hi Dale, I am aware of locking, but that requires I know all the recursive dependencies so I can lock them before loading the project itself. I can do that locally (and I've done it in the past), but I cannot easily force that upon users. This also applies for SmalltalkCI which will just try to

Re: [Pharo-dev] float & fraction equality bug

2017-11-10 1:18 GMT+01:00 : > On 2017-11-10 00:02, Henrik Sperre Johansen wrote: > > raffaello.giulietti wrote > >> On 2017-11-09 21:49, Stephane Ducasse wrote: > >>> On Thu, Nov 9, 2017 at 5:34 PM, Nicolas Cellier > >>> > > > >> nicolas.cellier.aka.nice@ > > >

Re: [Pharo-dev] float & fraction equality bug

2017-11-10 0:02 GMT+01:00 Henrik Sperre Johansen < henrik.s.johan...@veloxit.no>: > raffaello.giulietti wrote > > On 2017-11-09 21:49, Stephane Ducasse wrote: > >> On Thu, Nov 9, 2017 at 5:34 PM, Nicolas Cellier > >> > > > nicolas.cellier.aka.nice@ > > > wrote: > >>> Note that this started a