[Swift-devel] Code style
Michael Wilde
wilde at mcs.anl.gov
Tue May 14 13:33:04 CDT 2013
The internals/code-style page mentioned below is rather vague.
Im in favor of 3 things:
- code format inspired by K&R (more compact than {} on separate lines, while quite readable). The Oracle page cited by David is fine in that regard.
- spaces instead of hard tabs. I feel adamant about this.
- Ideally, a format for which some auto-formatter exists that would enable us to clean up our source.
Somehow the PBS provider files got very badly un-tabbed, so they are hard to read. We could at least fix the most offensive files. Does anyone have ideas on how to format all files without a massive SVN revision bump? Is a full sweep a bad idea?
- Mike
----- Original Message -----
> From: "David Kelly" <davidk at ci.uchicago.edu>
> To: "Swift Devel" <swift-devel at ci.uchicago.edu>
> Sent: Tuesday, May 14, 2013 1:24:24 PM
> Subject: [Swift-devel] Code style
>
>
>
>
> Hello,
>
>
> The topic of code style for internal Swift code came up this morning.
> On the swift-devel page, there is a document that describes how code
> should be formatted:
> https://sites.google.com/site/swiftdevel/internals/code-style. I
> think Justin wrote this document? I'm not sure we've ever discussed
> it much. Do people agree with these suggestions? Should we adopt
> this as our standard? Is it worth it go back to old code and
> reformat it?
>
>
> Another option may be something like the Oracle Java coding standard:
> http://www.oracle.com/technetwork/java/codeconvtoc-136057.html.
>
>
> David
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
More information about the Swift-devel
mailing list