By: justinohms

justinohms — Mon, 20 Jun 2011 17:26:51 +0000

You’re right… it does depend on the language. My SQL always tends to be more vertical and like you I tend to keep params one per line. I think I’ve realized where the difference is. I’ve been working a lot with MXML lately and I think this type of thing could become a problem there as well. In fact I tend to think that it is one of the issues with tag-based languages. Because tags can be nested but also have properties the layout of nested tags and named properties causes the issue. My preference is for readability over the tag, not the properties. I want to be able to quickly match up the start and end tags. This to me is more important than being able to quickly enumerate visually over the configuration properties for the tag. This means that ideally the tag pairs should be on the same screen with aligned indents. In code based languages, vertical layout considerations don’t need to be made to help locate tag pairs so there is more flexibility to use it to help readability in other areas such as parameters.

By: CantleyC

CantleyC — Fri, 15 Apr 2011 13:06:02 +0000

heh heh, I do this with my sql. Granted it is well indented but I hate having to hunt params horizontally in my stored procs.

That said, my CF code is not at all like that. I like to keep one tag on a line unless there are so many attributes that I bring it down a line and indent.

To each their own I guess. At least he is organized. I have dealt with some people who code like spaces and carriage returns are memory demons.

Comments on: Can your code be too structured?

By: justinohms

By: CantleyC