- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Re: about ifEmptyOrNil:

by Stefan Schmiedl

On Tue, 07 Oct 2008 23:54:02 +0100 Keith Hodges <keith_hodges(a)yahoo.co.uk> wrote: > After all purists don't have to interface to databases... do they? Or users: +-----------------------------------+ | | | Please enter your comment: | | | | __________________________ | | | | Ok Cancel | +-----------------------------------+ s.

Oct. 7, 2008

Re: [Pharo-project] Re: about ifEmptyOrNil:

by Keith Hodges

Rob Rothwell wrote: > Just today I was loading objects from an ODBCRow and wrote a: > > Collection>>addIfNotNilOrBlank ! > > Like you said...sometimes you get '', sometimes you get nil! > > Take care, > > Rob So... if it becomes something that every "pragmatic" user would like to add at least once in their coding lifetime, and the implementation is cleaner if done 'officially', why not have it as a useful evil. After all purists don't have to interface to databases... do they? Keith

Oct. 7, 2008

Re: [Pharo-project] Re: about ifEmptyOrNil:

by Rob Rothwell

Just today I was loading objects from an ODBCRow and wrote a: Collection>>addIfNotNilOrBlank ! Like you said...sometimes you get '', sometimes you get nil! Take care, Rob On Tue, Oct 7, 2008 at 6:02 PM, Keith Hodges <keith_hodges(a)yahoo.co.uk>wrote: > When I think about this issue in different terms I think it makes more > sense. No matter how perfect my code I find myself interfacing to things > like MySQL where it is happy to return nil when it means an empty string. > > someValue ifNotUsefulUse: [ defaultValue ]. > > but then the question "what does useful mean", at which point it becomes > easier to define clearly what is not useful i.e. > > someValue ifNilOrEmpty: [ defaultValue ]. > > If I had known this call existed I would use it much more because > > b := someValue ifEmpty: [ defaultValue ]. > > doesnt work (see earlier discussions on squeak-dev) > > regards > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 7, 2008

Re: [Pharo-project] Re: about ifEmptyOrNil:

by Keith Hodges

When I think about this issue in different terms I think it makes more sense. No matter how perfect my code I find myself interfacing to things like MySQL where it is happy to return nil when it means an empty string. someValue ifNotUsefulUse: [ defaultValue ]. but then the question "what does useful mean", at which point it becomes easier to define clearly what is not useful i.e. someValue ifNilOrEmpty: [ defaultValue ]. If I had known this call existed I would use it much more because b := someValue ifEmpty: [ defaultValue ]. doesnt work (see earlier discussions on squeak-dev) regards Keith

Oct. 7, 2008

Re: [Pharo-project] Re: about ifEmptyOrNil:

by StÃ©phane Ducasse

On Oct 6, 2008, at 11:28 PM, Michael Roberts wrote: > I agree with Lukas, and the other comments on the naming that really > you imply a test for nil first before the empty. My experience with > coming across and recalling heavy usage is that the receiver is always > a String. I took it to be a convenience (laziness) for typing the > longer form during string processing that is perhaps written in a > procedural manner. If the receiver is treated like a collection, i.e. > using do: select: etc then an empty collection is a fine null object. > Don't mind it being dropped, but perhaps it could remain on String? > Is the convenience justified? I can imagine that there are some cases where you want to make a distinction between no result and empty result from an UI perspective. But I learned something from this thread. And probably we should deprecated it. stef

Oct. 7, 2008

Re: [Pharo-project] Re: about ifEmptyOrNil:

by StÃ©phane Ducasse

> The arguments to not remove it are inertia as usual. > I see 163 senders in the 10074 image and probably many more in > Squeak packages. > Le ver est dans le fruit. I can understand that to manage cancel button the UI returns nil Now I do not see the gain with always returning '' even on cancel. > If you want to remove such message, it would be good to have a base of > refactoring rules to be applied on Squeak packages so that they > become Pharo > friendly. Sort of one-click compatibility automaton. Yes I will have probably to support that + a nice deprecated warning. On VW adrian kuhn did a deprecation that walk the stack and invoke the refactoring browser on the fly. This is something that we should do too. Stef

Oct. 7, 2008

Re: [Pharo-project] Polymorph

by StÃ©phane Ducasse

slick :) Stef On Oct 7, 2008, at 4:03 PM, Gary Chambers wrote: > Just to let you know there are some newer versions on SqueakSource. > Start of work on a "Watery 2" theme (more spotted cat like :-) ) > using CompositeFillStyles with form-based graphics. > A few other improvements too, check the version notes. > > Regards, Gary. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 7, 2008

Re: [Pharo-project] about idiots :)

by StÃ©phane Ducasse

On Oct 7, 2008, at 8:10 PM, Keith Hodges wrote: > StÃ©phane Ducasse wrote: >> Hi marcus >> >> Try to stop thinking that making errors is bad. >> This is a christian ideology that may block your way of looking at >> the >> world in a open way. > Not true at all. It might be a catholic ideology, but its not > christian. > > Christianity is about love, faith, and redemption. Not fear, fear is > the > opposite of faith. The whole point of christianity is to remove fear > from the equation, even the ultimate fear, fear of death. Ok sorry. catholic then :) > If you are a parent, would you want to provide a safe space to learn > and > grow, or to have your kids live in fear of making mistakes. > > I have counselled many perfectionists, and those who have suffered at > the hands of same, over the past few years, and God, being a father, > always tells them that it is ok to make mistakes, and not to be > afraid. > He is big enough to cover us and help us to work through the > consequences of our mistakes should they occur. Given that emotional > support, it is ok to make mistakes. > > >> >> So do not let you fun gets spoiled by this oversimplistic view on the >> world. >> > Agreed one would not want to oversimplify by blaming some "ideology" > for > all our problems. > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 7, 2008

[Pharo-project] update10074 hashMappedBy: not removed as advertised

by nicolas cellier

Hello all, second try to post this message, sorry if it duplicates. When I select hashMappedBy: in the 10074 Workspace and press alt+b I can still see 5 implementors. Seems like a change has been forgotten...

Oct. 7, 2008

[Pharo-project] Re: Some clearifications

by Markus Fritsche

Adrian Lienhard schrieb: > In other words, this is not a version you want to use to run a power plant. Can you please put me on the list for the day this changes? I'm having a power plant in my backyard and I'm still searching something to run it with... scnr, Markus P.S.: I hope you forgive the white noise, but in this case, I just cnr...

Oct. 7, 2008