Re: Re: Re: Non-destructive array processing

unusable within a work/production context

I wouldn't handle large data sets in production code. This is primarily for one-time hacks, but I wondered what other people would prefer.

No maintenance programmer is going to get confused years after ive left the company.

Note that if code like this ever goes into production, I do of course add proper comments, including a note that you shouldn't use @$r elsewhere (re your other post).

Juerd
- http://juerd.nl/
- spamcollector_perlmonks@juerd.nl (do not use).

Comment on Re: Re: Re: Non-destructive array processing

Replies are listed 'Best First'.
Re: Re: Re: Re: Non-destructive array processing by demerphq (Chancellor) on Jan 22, 2003 at 00:59 UTC
I do of course add proper comments I think the point is that its better not to have to comment at all. If the code looks like it does what it does then you dont need a comment. Plus comments get out of date sometimes and then cause confusion. I realize that a well chosen comment can be extremely useful, but I think you know what I mean. shrug Its a nice trick though for some things. :-) Although Ive usually used it as named routine. `sub aliased_array { \@_ }` [download] --- demerphq my friends call me, usually because I'm late....	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Re: Re: Non-destructive array processing
by demerphq (Chancellor) on Jan 22, 2003 at 00:59 UTC

I do of course add proper comments

I think the point is that its better not to have to comment at all. If the code looks like it does what it does then you dont need a comment. Plus comments get out of date sometimes and then cause confusion. I realize that a well chosen comment can be extremely useful, but I think you know what I mean.

*shrug* Its a nice trick though for some things. :-) Although Ive usually used it as named routine.

sub aliased_array { \@_ }
[download]

--- demerphq
my friends call me, usually because I'm late....

[reply]
[d/l]