- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] pharo --help returning non-zero exit status

by Stephane Ducasse

Sure. It probably skipped Esteban view. On Tue, Oct 3, 2017 at 9:37 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > Having the discussions scattered in Pharo-dev vm-dev github may help > extending the indecision phase... > > There has been another important thread in vm-dev (Validation builds > failing) > http://lists.squeakfoundation.org/pipermail/vm-dev/2017-June/025417.html > > The conclusion was that we ask for some Pharo authority to approve the > change > We thus asked for Esteban's blessing, but unfortunately it seems that you > have assigned much more work to Esteban without taking the precaution to > clone him first... IMO you need about 4 or 5 Esteban. > > If Pharo is OK, then we can just accept the PR and clean a bit the list of > stale PR > > 2017-10-02 15:21 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> Esteban, Eliot, Clement was is the process to get this fix in the VM? >> >> On Sun, Oct 1, 2017 at 9:05 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> > Ah, perfect. Thanks! >> > >> > peter >> > >> > On Sun, Oct 1, 2017 at 8:41 AM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >> >> >> >> On Sunday 01 October 2017 11:27 AM, Peter UhnÃ¡k wrote: >> >>> >> >>> Hi, >> >>> >> >>> why does executing `pharo --help` return exit status 1? The operation >> >>> succeeded, so I don't see a reason for a failure return state. >> >> >> >> >> >> This is a bug. See the thread at >> >> >> >> >> >> >> >> >> >> http://forum.world.st/Re-Pharo-dev-pharo-help-returns-exit-code-1-on-ubuntu… >> >> >> >> The proposed fix is pending review at: >> >> >> >> https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/136 >> >> >> >> Regards .. Subbu >> >> >> >> >> > >> >

Oct. 5, 2017

Spec enhancements

by Stephane Ducasse

Hi rob I like you extensions to label and text. I harvested them with the tests and I will slowly generalise that to other widgets. I published my current code experiments to MCSmalltalkhubRepository owner: 'Pharo' project: 'Spec' user: '' password: '' Stef

Oct. 5, 2017

Re: [Pharo-dev] Reproducible VM Crash using UFFI

by Esteban Lorenzano

> On 5 Oct 2017, at 08:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > H Hernani, oopsâ¦ Hernanâ¦ too early in the morning here ;) > Most probably is a problem in the library and not UFFI, but I could not know without a crash report. > > Esteban > >> On 5 Oct 2017, at 06:00, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >> Hi, >> >> I ported Nacl (a libsodium wrapper) from the old FFI apicall: format >> to use the UFFI ffiCall:, but there should be something terribly wrong >> because is crashing the VM, in both Windows 8.1 and Linux. >> >> How to reproduce in Pharo 6.1 >> >> Metacello new >> smalltalkhubUser: 'tonyg' project: 'Crypto-Nacl'; >> configuration: 'Nacl'; >> version: #development; >> load. >> >> (Nacl hashString: 'The quick brown fox jumps over the lazy dog') hex >> >> This one does deserve a bug entry? >> >> Cheers, >> >> HernÃ¡n >> >

Oct. 5, 2017

Re: [Pharo-dev] Reproducible VM Crash using UFFI

by Esteban Lorenzano

H Hernani, Most probably is a problem in the library and not UFFI, but I could not know without a crash report. Esteban > On 5 Oct 2017, at 06:00, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi, > > I ported Nacl (a libsodium wrapper) from the old FFI apicall: format > to use the UFFI ffiCall:, but there should be something terribly wrong > because is crashing the VM, in both Windows 8.1 and Linux. > > How to reproduce in Pharo 6.1 > > Metacello new > smalltalkhubUser: 'tonyg' project: 'Crypto-Nacl'; > configuration: 'Nacl'; > version: #development; > load. > > (Nacl hashString: 'The quick brown fox jumps over the lazy dog') hex > > This one does deserve a bug entry? > > Cheers, > > HernÃ¡n >

Oct. 5, 2017

Reproducible VM Crash using UFFI

by HernÃ¡n Morales Durand

Hi, I ported Nacl (a libsodium wrapper) from the old FFI apicall: format to use the UFFI ffiCall:, but there should be something terribly wrong because is crashing the VM, in both Windows 8.1 and Linux. How to reproduce in Pharo 6.1 Metacello new smalltalkhubUser: 'tonyg' project: 'Crypto-Nacl'; configuration: 'Nacl'; version: #development; load. (Nacl hashString: 'The quick brown fox jumps over the lazy dog') hex This one does deserve a bug entry? Cheers, HernÃ¡n

Oct. 5, 2017

About Pragma comment and Pragma description

by Stephane Ducasse

Hi, That is my proposal as well: introduce a first class entity that describes a Pragma instance. Who would be interested to play with this? Cheers, Doru Doru where can I find the code?

Oct. 4, 2017

Re: [Pharo-dev] String Interpolation

by Esteban A. Maringolo

2017-10-04 16:49 GMT-03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > 2017-10-04 21:38 GMT+02:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: >>> It is not compiled time but behaviour is very close to it. >>> The trick is that first time execution will replace full expression with >>> the result as literal (the receiver of #asMethodConst). So at second time it >>> will be just literal reading. >> It is weird that a regular message send makes the returned value a method >> constant. >> How is that cleaned up? Do I have to search for all the methods that >> contain such message send? > What the problem? This message is a tool. You use it when you need it. When > you modify the method the value is cleaned. > Nice thing is that it not requires special syntax. And you can debug > expression as normal part of method. I don't see any problem, I just said "weird". It's a "special return" message send. A trick of sorts, no different than #doesNotUnderstand: or other special selectors. Regards, Esteban A. Maringolo

Oct. 4, 2017

Deprecating ValueHolder (call for Spec user)

by Stephane Ducasse

Hi we have ValueHolder and NewValueHolder so I wanted to remove the 6 last user of ValueHolder. Now I see that we have ValueHolder >> contents: newContents contents := newContents. self changed: #contents NewValueHolder >> value: anObject self handleCircularReferencesWhile: [ | oldValue | oldValue := value. value := anObject. self valueChanged: oldValue ]. ^ value So dialog newSliderFor: (ValueHolder new contents: 0.5) getValue: #contents setValue: #contents: help: 'This is a slider'). => (dialog newSliderFor: (NewValueHolder new value: 0.5; yourself) getValue: #value setValue: #value: help: 'This is a slider'). and I find that boring to have to be forced to use yourself. as an experiment I changed the definition of value: to NewValueHolder >> value: anObject self handleCircularReferencesWhile: [ | oldValue | oldValue := value. value := anObject. self valueChanged: oldValue ]. Now I'm looking for spec users to tell me if I break something. Stef

Oct. 4, 2017

Re: [Pharo-dev] String Interpolation

by Denis Kudriashov

2017-10-04 21:38 GMT+02:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > 2017-10-04 6:46 GMT-03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> Hi Igor. >> >> Did you see that we have now #asMethodConstant? >> >> DateAndTime now asMethodConst >> >> >> It is not compiled time but behaviour is very close to it. >> The trick is that first time execution will replace full expression with >> the result as literal (the receiver of #asMethodConst). So at second time >> it will be just literal reading. >> >> > It is weird that a regular message send makes the returned value a method > constant. > How is that cleaned up? Do I have to search for all the methods that > contain such message send? > What the problem? This message is a tool. You use it when you need it. When you modify the method the value is cleaned. Nice thing is that it not requires special syntax. And you can debug expression as normal part of method. > > Dolphin had the ##() syntax, which basically creates a method constant, > but it is evaluated right away. > > So you could write the seconds in a day as ##(60*60*24), or, of course, > any more complex expression. But the difference is that it is resolved at > compile time. > > However I don't see how this relates with the String interpolation :) > > Esteban A. Maringolo > > > >

Oct. 4, 2017

Re: [Pharo-dev] String Interpolation

by Esteban A. Maringolo

2017-10-04 6:46 GMT-03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hi Igor. > > Did you see that we have now #asMethodConstant? > > DateAndTime now asMethodConst > > > It is not compiled time but behaviour is very close to it. > The trick is that first time execution will replace full expression with > the result as literal (the receiver of #asMethodConst). So at second time > it will be just literal reading. > > It is weird that a regular message send makes the returned value a method constant. How is that cleaned up? Do I have to search for all the methods that contain such message send? Dolphin had the ##() syntax, which basically creates a method constant, but it is evaluated right away. So you could write the seconds in a day as ##(60*60*24), or, of course, any more complex expression. But the difference is that it is resolved at compile time. However I don't see how this relates with the String interpolation :) Esteban A. Maringolo

Oct. 4, 2017