[Pharo-project] Compiler pedantic about ifNotNil: argument

Randal L. Schwartz merlyn at stonehenge.com
Mon Oct 11 11:37:11 EDT 2010


>>>>> "Lukas" == Lukas Renggli <renggli at gmail.com> writes:

Lukas> 1. It is not easily understandable for newbies.
Lukas> 2. It quickly leads to very unreadable, hard to understand and hard to
Lukas> refactor code.
Lukas> 3. It is very limiting in itself and quickly leads to other hacks
Lukas> (like to replace sort blocks).
Lukas> 4. #value and friends should be only understood by objects that can be
Lukas> evaluated (certainly not by Object). A symbol (name) by itself cannot
Lukas> be evaluated.

+1

Lukas> If people are too lazy to create a block where something
Lukas> self-evaluable is needed they should use a programming language
Lukas> designed for cryptic code. Creating a block closure in Smalltalk is
Lukas> concise and makes clear what happens easily. A symbol does not, you
Lukas> need to exactly understand how this dispatches with various
Lukas> objects.

Agreed.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion




More information about the Pharo-dev mailing list