Re^2: What is code readability?

I tend to dislike the practice of splitting long lines before operators,

Well it depends on the situation in your example it is not such a big deal. However, problems occur when lines tend run long. Example:

# Long line
my $absolutely_very_long_value = $value_reference->{$first_record}{$se
+cond_key}{super_property} + $value_reference->{$second_record}{$secon
+d_key}{super_property};

# Split Line
my $absolutely_very_long_value 
  = $value_reference->{$first_record }{$second_key}{super_property} 
  + $value_reference->{$second_record}{$second_key}{super_property};
[download]

I think the worst example for a long-line is something like this,

my $print = qq~
# HTML that goes on for 30+ lines
# This some more text here. text text text text text text text~ if $in
+s{save_changes};
[download]

I could have strung up the original programmer for this. This sort of syntax you may not even know you are working on a if statement. You don't see it unless you page down or you have to scroll all the way to the right.

Comment on Re^2: What is code readability? Select or Download Code

Replies are listed 'Best First'.

Re^3: What is code readability?
by swampyankee (Parson) on Jan 03, 2007 at 16:33 UTC

Well it depends on the situation in your example it is not such a big deal. However, problems occur when lines tend run long.

I just prefer to split lines after operators.

In your example, my code would look like this:

# split line
my $absolutely_very_long_value =
   $value_reference -> {$first_record}{$second_key}{super_property} +
   $value_reference -> {$second_record}{$second_key}{super_property};
[download]

emc

At that time [1909] the chief engineer was almost always the chief test pilot as well. That had the fortunate result of eliminating poor engineering early in aviation.

—Igor Sikorsky, reported in AOPA Pilot magazine February 2003.

[reply]
[d/l]


The stupid question is the question not asked
	PerlMonks