Oct. 10, 2015
4:55 p.m.
Collection>>ifNotEmpty: comment says "If the block has an argument, eval with the receiver as its argument, but it might be better to use ifNotEmptyDo: to make the code easier to understand" yet when I do that, Code Critic complains: ifNotEmptyDo: should not be used as ifNotEmpty: works for blocks with arguments, too. 1) who is right? what should I use? 2) shouldn't one be deprecated then? (or maybe one of them is to be compatible with other smalltalks?) Thanks, Peter