Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [openj9-dev] Code reformatting

I like most of it. I'm not a big fan of
1. the way the || gets put into its own line here https://github.com/rwy0717/openj9-reformat/blob/594367c71f6e22e5df5d0faedd5a84d54eb0c2d1/runtime/compiler/control/CompilationThread.cpp#L456-L464
2. the way the commas are before the next parameter here https://github.com/rwy0717/openj9-reformat/blob/594367c71f6e22e5df5d0faedd5a84d54eb0c2d1/runtime/compiler/runtime/SymbolValidationManager.hpp#L508-L509

However, these are minor grievances that I'll gladly put aside, as I think the benefit of having a consistent standard outweighs any individual subjective concern(s). Also FWIW, I don't care whether it's tabs or spaces; an IDE can easily be configured so that any perceived inconveniences are minimized.

Regards,


Irwin D'Souza
JIT Compiler Developer
IBM Runtime Technologies
Email: dsouzai@xxxxxxxxxx
Phone: 905-413-2956


Inactive hide details for "Daniel Heidinga" ---12/20/2018 03:32:21 PM---And here's the reformatted OpenJ9 repo:  https://github"Daniel Heidinga" ---12/20/2018 03:32:21 PM---And here's the reformatted OpenJ9 repo: https://github.com/rwy0717/openj9-reformat/tree/master/runt

From: "Daniel Heidinga" <Daniel_Heidinga@xxxxxxxxxx>
To: openj9-dev@xxxxxxxxxxx
Cc: openj9-dev@xxxxxxxxxxx
Date: 12/20/2018 03:32 PM
Subject: Re: [openj9-dev] Code reformatting
Sent by: openj9-dev-bounces@xxxxxxxxxxx





And here's the reformatted OpenJ9 repo: https://github.com/rwy0717/openj9-reformat/tree/master/runtime

Only the C/C++ code under the /runtime directory has been reformatted. Please review for critical concerns with readability / clarity in the formatted code.

Thanks Rob!

--Dan

----- Original message -----
From: "Daniel Heidinga" <Daniel_Heidinga@xxxxxxxxxx>
Sent by: openj9-dev-bounces@xxxxxxxxxxx
To: openj9-dev@xxxxxxxxxxx
Cc:
Subject: [openj9-dev] Code reformatting
Date: Thu, Dec 20, 2018 2:29 PM

There's a discussion at the Eclipse OMR project about reformatting their code base to use a consistent style. Given the close history between the two projects and overlap in the developer communities, I can see a lot of benefits to having the same coding format between the two projects.

I'd like to get some feedback on whether we should follow suit and reformat OpenJ9 as well. The area I'm most interested in is whether there are any concrete problems we might encounter with a full reformat. Please raise any logistics questions on list.

Remember, most of code formatting is personal preference. Let's only call out areas that are critical concerns with readability / clarity in the formatted code.

Rob has agreed to run the formatter on the OpenJ9 code base as well so we can see how the code looks post-format. Links to the PR / formatted repo will be shared once available.

Timeline for OpenJ9 would need to be post-0.12.0 with a soft target of mid February assuming there's agreement to go forward here.

Thanks,
--Dan

----- Original message -----
From: Robert Young <rwy0717@xxxxxxxxx>
Sent by: omr-dev-bounces@xxxxxxxxxxx
To: omr developer discussions <omr-dev@xxxxxxxxxxx>
Cc:
Subject: Re: [omr-dev] our coding standard
Date: Thu, Dec 20, 2018 1:06 PM

I'd like to reopen the discussion on adopting a common coding standard. Based on the original discussion (which took place over two years ago), we're looking at adopting clang-format based tooling to implement a webkit-style format. I've opened PR #3390 which adds a .clang-format to the root of OMR. The PR has more information and links to code samples. Please take a look!

https://github.com/eclipse/omr/pull/3390

During (and immediately after) the winter break, there is usually a lull in development. Now might be our best chance to reformat the codebase, and minimize the negative impact on developers. If we can finalize a common clang-format now, then we can start migrating code to the new format early in the new year.

- Rob

noname
_______________________________________________
omr-dev mailing list
omr-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/omr-dev


_______________________________________________
openj9-dev mailing list
openj9-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/openj9-dev

_______________________________________________
openj9-dev mailing list
openj9-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/openj9-dev




Back to the top