- Pharo-users - lists.pharo.org

Re: [Pharo-users] How does Boolean ifTrue work?

by Norbert Hartl

> Am 31.10.2016 um 15:59 schrieb phil(a)highoctane.be: > > but you should use myCollection ifEmpty: [ ... ] > Why? Norbert > Phil > > On Mon, Oct 31, 2016 at 3:25 PM, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > myCollection isEmpty ifTrue: [ self inform: 'The collection is empty' ]. > > First #isEmpty is sent to myCollection which results in either true or false as value. > > Then #ifTrue: is sent to this value. > > Now, if the value was true (the sole instance of class True), the code in True>>#ifTrue: is executed, which will evaluate the block by sending it #value. If the value was false, the code in False>>#ifTrue: is executed, and nil is returned and the block is not executed. > > Like others said, it is just polymorphism at work. > > (And yes, the compiler optimises some of this logic a bit, but the effect is the same). > > > On 31 Oct 2016, at 14:58, CodeDmitry <dimamakhnin(a)gmail.com <mailto:dimamakhnin@gmail.com>> wrote: > > > > But still, how is the actual argument "alternativeBlock" passed to the > > True/False from a Boolean? > > > > The message does not cache the message inside itself before passing the > > message, and it does not pass the alternative block along with the message. > > > > > > > > -- > > View this message in context: http://forum.world.st/How-does-Boolean-ifTrue-work-tp4920873p4920886.html <http://forum.world.st/How-does-Boolean-ifTrue-work-tp4920873p4920886.html> > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > >

Oct. 31, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by Esteban A. Maringolo

2016-10-31 11:32 GMT-03:00 CodeDmitry <dimamakhnin(a)gmail.com>: > I realized it a bit before you posted but thanks for confirming. > > Boolean seems to indeed just be a "Dynamic Interface"; since Smalltalk does > not have "Java Interfaces"(nor want them for the same reason JavaScript > doesn't), the developers wanted to still have True and False be subclasses > of Booleans. > > In all honesty Boolean seems to be there purely for the "common sense" of > it, rather than need. Smalltalk is duck typed and has no need for > interfaces. If it's a Boolean, you know it has those methods so Boolean is > not actually useful for anything; True and False may as well just be > subclasses of Object. Not exactly, look at the methods in Boolean and you'll see many methods are common to all. So Boolean has a reason to be the superclass of both True and False. Esteban A. Maringolo

Oct. 31, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by Thierry Goubier

Le 31/10/2016 Ã 15:32, CodeDmitry a Ã©crit : > I realized it a bit before you posted but thanks for confirming. > > Boolean seems to indeed just be a "Dynamic Interface"; since Smalltalk does > not have "Java Interfaces"(nor want them for the same reason JavaScript > doesn't), the developers wanted to still have True and False be subclasses > of Booleans. Boolean is a nice header for classification. Everybody is familiar with Boolean algebra, including hardware guys :) > In all honesty Boolean seems to be there purely for the "common sense" of > it, rather than need. Smalltalk is duck typed and has no need for > interfaces. If it's a Boolean, you know it has those methods so Boolean is > not actually useful for anything; True and False may as well just be > subclasses of Object. Not exactly. Boolean carry 15 methods that are not overridden in either False nor True (and 11 methods which are), so Boolean is also used as a way to share code between the classes True and False and avoid code duplication. A nice case for having a common superclass below Object. Thierry

Oct. 31, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by phil＠highoctane.be

For the full story, these objects and ifTrue: etc are special cases in the VM code. For speed. Phil On Mon, Oct 31, 2016 at 3:32 PM, CodeDmitry <dimamakhnin(a)gmail.com> wrote: > I realized it a bit before you posted but thanks for confirming. > > Boolean seems to indeed just be a "Dynamic Interface"; since Smalltalk does > not have "Java Interfaces"(nor want them for the same reason JavaScript > doesn't), the developers wanted to still have True and False be subclasses > of Booleans. > > In all honesty Boolean seems to be there purely for the "common sense" of > it, rather than need. Smalltalk is duck typed and has no need for > interfaces. If it's a Boolean, you know it has those methods so Boolean is > not actually useful for anything; True and False may as well just be > subclasses of Object. > > > > > > -- > View this message in context: http://forum.world.st/How- > does-Boolean-ifTrue-work-tp4920873p4920891.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >

Oct. 31, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by phil＠highoctane.be

but you should use myCollection ifEmpty: [ ... ] Phil On Mon, Oct 31, 2016 at 3:25 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > myCollection isEmpty ifTrue: [ self inform: 'The collection is empty' ]. > > First #isEmpty is sent to myCollection which results in either true or > false as value. > > Then #ifTrue: is sent to this value. > > Now, if the value was true (the sole instance of class True), the code in > True>>#ifTrue: is executed, which will evaluate the block by sending it > #value. If the value was false, the code in False>>#ifTrue: is executed, > and nil is returned and the block is not executed. > > Like others said, it is just polymorphism at work. > > (And yes, the compiler optimises some of this logic a bit, but the effect > is the same). > > > On 31 Oct 2016, at 14:58, CodeDmitry <dimamakhnin(a)gmail.com> wrote: > > > > But still, how is the actual argument "alternativeBlock" passed to the > > True/False from a Boolean? > > > > The message does not cache the message inside itself before passing the > > message, and it does not pass the alternative block along with the > message. > > > > > > > > -- > > View this message in context: http://forum.world.st/How- > does-Boolean-ifTrue-work-tp4920873p4920886.html > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > >

Oct. 31, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by CodeDmitry

Ah so it's more of a "dynamic abstract class" than a "dynamic interface", so they do get visited during the traversal of the inheritence chain(rather than skipped immediately to Object). -- View this message in context: http://forum.world.st/How-does-Boolean-ifTrue-work-tp4920873p4920896.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Oct. 31, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by CodeDmitry

I realized it a bit before you posted but thanks for confirming. Boolean seems to indeed just be a "Dynamic Interface"; since Smalltalk does not have "Java Interfaces"(nor want them for the same reason JavaScript doesn't), the developers wanted to still have True and False be subclasses of Booleans. In all honesty Boolean seems to be there purely for the "common sense" of it, rather than need. Smalltalk is duck typed and has no need for interfaces. If it's a Boolean, you know it has those methods so Boolean is not actually useful for anything; True and False may as well just be subclasses of Object. -- View this message in context: http://forum.world.st/How-does-Boolean-ifTrue-work-tp4920873p4920891.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Oct. 31, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by Sven Van Caekenberghe

myCollection isEmpty ifTrue: [ self inform: 'The collection is empty' ]. First #isEmpty is sent to myCollection which results in either true or false as value. Then #ifTrue: is sent to this value. Now, if the value was true (the sole instance of class True), the code in True>>#ifTrue: is executed, which will evaluate the block by sending it #value. If the value was false, the code in False>>#ifTrue: is executed, and nil is returned and the block is not executed. Like others said, it is just polymorphism at work. (And yes, the compiler optimises some of this logic a bit, but the effect is the same). > On 31 Oct 2016, at 14:58, CodeDmitry <dimamakhnin(a)gmail.com> wrote: > > But still, how is the actual argument "alternativeBlock" passed to the > True/False from a Boolean? > > The message does not cache the message inside itself before passing the > message, and it does not pass the alternative block along with the message. > > > > -- > View this message in context: http://forum.world.st/How-does-Boolean-ifTrue-work-tp4920873p4920886.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Oct. 31, 2016

Re: [Pharo-users] How does Boolean ifTrue work?

by Thierry Goubier

Le 31/10/2016 Ã 14:58, CodeDmitry a Ã©crit : > But still, how is the actual argument "alternativeBlock" passed to the > True/False from a Boolean? > > The message does not cache the message inside itself before passing the > message, and it does not pass the alternative block along with the message. If I get correctly what you are saying, this is because the ifTrue:ifFalse: message is never sent to an instance of Boolean. It is sent either to true, the single instance of class True, or to false, the single instance of class False, where the implementation is what you expect: False>>#ifTrue:ifFalse: ifTrue: trueAlternativeBlock ifFalse: falseAlternativeBlock "Answer the value of falseAlternativeBlock. Execution does not actually reach here because the expression is compiled in-line." ^falseAlternativeBlock value If you're interested in the details, do also read the comment. Regards, Thierry

Oct. 31, 2016

Re: [Pharo-users] Spec: Setting rows height of a pictures list

by Nicolai Hess

2016-10-31 15:07 GMT+01:00 Matteo via Pharo-users < pharo-users(a)lists.pharo.org>: > > > ---------- Weitergeleitete Nachricht ---------- > From: Matteo <matteob8(a)yahoo.it> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Cc: > Date: Mon, 31 Oct 2016 15:06:27 +0100 > Subject: Re: [Pharo-users] Spec: Setting rows height of a pictures list > Thanks Nicolai, > > unfortunately, even using images of the same height I obtain a list > with thin rows. Maybe I'm typing something wrong. > > I'll try to figure out how to handle this. > Please let me know, if you have any further suggestion. > > Thanks, > Matteo > > For Images with the same height/width, you can use #buildWithSpecLayout: in the displayBlock and use a SpecTableLayout with the width/height of the image model image. But this doesn't really work, somehow the list widget can not handle the selection and scrolling (but the images are shown in full size) : imageModels := (1 to:10) collect:[:i | ImageModel new image: PolymorphSystemSettings pharoLogoForm]. listModel := ListModel new items: imageModels. listModel displayBlock:[:item | | layout | layout := SpecTableLayout row add:#yourself; height: item image height; width: item image width. item buildWithSpecLayout: layout]. listModel openWithSpec > > On 31/10/16 12:26, Nicolai Hess wrote: > > > > > > 2016-10-31 10:19 GMT+01:00 Matteo via Pharo-users > > <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>>: > > > > > > > > ---------- Weitergeleitete Nachricht ---------- > > From: Matteo <matteob8(a)yahoo.it <mailto:matteob8@yahoo.it>> > > To: "Pharo is welcome (ML)" <pharo-users(a)lists.pharo.org > > <mailto:pharo-users@lists.pharo.org>> > > Cc: > > Date: Mon, 31 Oct 2016 10:18:03 +0100 > > Subject: Spec: Setting rows height of a pictures list > > Hi, > > I've created a list of pictures, i.e. a widget based on > > ListModel where > > each item is a ImageModel. > > > > When the widget is displayed I get list window with very > > thin rows. > > > > Is there a way to control the ListModel rows height? > > > > > > Not if the images have different heights (you can, but it looks > > terrible, because the underlaying list morph does not work for list > > items with different heights). > > > > > > > > > > Thanks, > > Matteo > > > > > > > > >

Oct. 31, 2016