Re: How would you indent this?

Replies are listed 'Best First'.
Re^2: How would you indent this? by no longer just digit (Beadle) on Mar 18, 2021 at 05:34 UTC
The cperl-mode default is awful. It's probably a bug or at least unintentional behaviour. It seems like the consensus is that one should either have `{key => 'k', class => 'kanji'},` [download] or `{ key => 'k', class => 'kanji', },` [download] but not `{ key => 'k', class => 'kanji' },` [download] so what I should do is to stop it from adding the newline after the {.	[reply] [d/l] [select]
Re^3: How would you indent this? by ikegami (Patriarch) on Mar 18, 2021 at 07:32 UTC
`{ key => 'k', class => 'kanji' },` [download] is best here because it makes it easy to see the differences the rows at a glance. `{ key => 'k', class => 'kanji' },` [download] isn't too bad, since it's almost as good at showing the differences between rows. The extra spacing is a needless hindrance, though, so it's not as good. But it's definitely not as bad as what you posted in the OP. `{ key => 'k', class => 'kanji' },` [download] This is just plain weird. Finally, we have this: `{ key => 'k', class => 'kanji', },` [download] It offers no readability benefits over the styles, and makes it even harder to see differences between the lines. No good here. This would be used when dealing with with very long records, and when adjacent lines are substantially different (e.g. in a multi-level structure). Seeking work! You can reach me at ikegami@adaelis.com	[reply] [d/l] [select]
Re^4: How would you indent this? by LanX (Saint) on Mar 18, 2021 at 19:23 UTC
> Finally, we have this: `{ key => 'k', class => 'kanji', },` [download] > It offers no readability benefits over the styles, and makes it even harder to see differences between the lines. I'd say that's the reasonable default, the => should be vertically aligned tho. Everything else needs intelligent heuristics to determine if the data has a repeated structure requiring another presentation. (not all AoHs have a nearly tabular semantic like in the OP's case) That's why all these Data::* modules are so complicated. And only the author can tell what the best representation is. An editor shouldn't change manual formatting. Problem in this thread is that the OP is effectively asking multiple questions: how should this be best written how should my editor do it what's the bug in my editor Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply] [d/l]
Re^5: How would you indent this? by GrandFather (Saint) on Mar 18, 2021 at 20:24 UTC
Re^6: How would you indent this? by LanX (Saint) on Mar 18, 2021 at 20:48 UTC
Some notes below your chosen depth have not been shown here
Re^5: How would you indent this? by ikegami (Patriarch) on Mar 19, 2021 at 13:32 UTC
Re^6: How would you indent this? by LanX (Saint) on Mar 19, 2021 at 14:04 UTC
Some notes below your chosen depth have not been shown here
Re^4: How would you indent this? by Anonymous Monk on Mar 19, 2021 at 08:46 UTC
You seem to place too much emphasis on needing "to see differences between the lines" esp at a glance -- source code is too verbose for that kind of analysis, instead use spreadsheet or printf	[reply]
Re^5: How would you indent this? by ikegami (Patriarch) on Mar 19, 2021 at 13:41 UTC
Re^6: How would you indent this? by Anonymous Monk on Mar 20, 2021 at 02:43 UTC
Some notes below your chosen depth have not been shown here
Re^3: How would you indent this? by parv (Parson) on Mar 18, 2021 at 07:18 UTC
My issue with first and last styles is that changes needlessly become cumbersome. That may be preferred to set infrequently changing defaults, or if one needs to save precious vertical space.	[reply]


Just another Perl shrine
	PerlMonks