Difference between revisions of "Talk:Eiffel Coding Standard"
(New page: --~~~~: I always wondered why classes formatted by EiffelStudio have such formatting inconsistency: keywords at the top level are sometimes followed by an empty line (e.g. 'feature') and s...) |
Peter gummer (Talk | contribs) |
||
Line 1: | Line 1: | ||
--[[User:Ericb|Ericb]] 08:25, 21 July 2009 (UTC): I always wondered why classes formatted by EiffelStudio have such formatting inconsistency: keywords at the top level are sometimes followed by an empty line (e.g. 'feature') and sometimes not (e.g. 'inherit', 'create'). In Gobo the formatting is consistent regardless of which top level construct of the class: all top level keywords are followed by an empty line. | --[[User:Ericb|Ericb]] 08:25, 21 July 2009 (UTC): I always wondered why classes formatted by EiffelStudio have such formatting inconsistency: keywords at the top level are sometimes followed by an empty line (e.g. 'feature') and sometimes not (e.g. 'inherit', 'create'). In Gobo the formatting is consistent regardless of which top level construct of the class: all top level keywords are followed by an empty line. | ||
+ | |||
+ | --[[User:Peter gummer|Peter gummer]] 01:06, 22 July 2009 (UTC) I've never considered this an inconsistency, Eric. EiffelStudio never puts an empty line after a top-level keyword, except after 'feature'. The reason for this exception looks obvious to my eyes: there is always one empty line above and below each feature. In other words, it's not really an exception to the rule at all, because the features ''do'' commence on the line immediately after the keyword 'feature'; the empty line is actually part of the list of features. This certainly looks more right to my eyes than the Gobo style of formatting. |
Revision as of 17:06, 21 July 2009
--Ericb 08:25, 21 July 2009 (UTC): I always wondered why classes formatted by EiffelStudio have such formatting inconsistency: keywords at the top level are sometimes followed by an empty line (e.g. 'feature') and sometimes not (e.g. 'inherit', 'create'). In Gobo the formatting is consistent regardless of which top level construct of the class: all top level keywords are followed by an empty line.
--Peter gummer 01:06, 22 July 2009 (UTC) I've never considered this an inconsistency, Eric. EiffelStudio never puts an empty line after a top-level keyword, except after 'feature'. The reason for this exception looks obvious to my eyes: there is always one empty line above and below each feature. In other words, it's not really an exception to the rule at all, because the features do commence on the line immediately after the keyword 'feature'; the empty line is actually part of the list of features. This certainly looks more right to my eyes than the Gobo style of formatting.