Re: [FWP] Changing the subject (was: Badly written code)

[Tushar Samant <D@i-works.com>]

On Sun, 7 Nov 1999, Yitzchak Scott-Thoennes wrote:
>I'd like to share the following with you all. [...]

[grep in void context]

This is sort of nice to know, because it never bothered me either.
Actually I stopped reading, um, certain newsgroups because an
inexplicably large number of people WERE bothered by things like
this--enough to flame mercilessly. I think grep in void context,
confusing list and array, stringifying a string, unnecesary quotes
in a hash lookup ($hash{'key'}), local instead of my, indirect
object syntax for new(), etc etc just don't make a damn bit of
difference most of the time.


>Subject: Re: grep/map in void context
>In article <199911012346.PAA25557@kiev.wall.org>,
>Larry Wall <larry@wall.org> wrote:
>>hv@crypt0.demon.co.uk writes:
>>: Isn't the point that (void)'grep EXPR, LIST' is now better written as
>>: 'EXPR for LIST'? Or am I misunderstanding your point here?
>>
>>It really doesn't bother me if people want to use grep or map in a void
>>context.  It didn't bother me before there was a for modifier, and
>>now that there is one, it still doesn't bother me.  I'm just not very
>>easy to bother.
>>
>>The argument against using an operator for other than its primary
>>purpose strikes me the same as the old argument that you shouldn't have
>>sex for other than procreational purposes.  Sometimes side effects
>>are more enjoyable than the originally intended effect.
>>
>>That being said, I'd never grep someone in a void context myself.
>>
>>Larry


==== Want to unsubscribe from Fun With Perl?  Well, if you insist...
==== Send email to <fwp-request@technofile.org> with message _body_
====   unsubscribe