Rick Klement <[EMAIL PROTECTED]> wrote:
> I write it this way (corrected) (with tabs and TS=2 in vim):
>
> if (...)
> {
> my @item_parts = split(/\n/, $item);
> printf ORDER ("\n%4d %-50s %3.2f %3.2f\n",
> $quantity, $item_parts[0], $price, $ext);
> }
> else
> {
> printf ORDER ("\n%4d %-50s %3.2f %3.2f\n",
> $quantity, $item, $price, $ext);
> }
>
> It makes the problem obvious... :)
Well, what I said was true. I wasn't familiar with that style.
Perhaps I've led a sheltered life. I guess you're right that
it avoids the problem, as long as you never have more than one
tab level of indenting for the second line of a statement. But
then if you never have a greatly indented second line (and thus
never worry about lining things up), the problem won't be very
likely regardless of your indenting style.
Since I have never encountered the problem and am quite happy
with my own, standard indenting style, I see no reason to
change. But we're venturing into unfun territory.
--
Keith C. Ivey <[EMAIL PROTECTED]>
Washington, DC
