[ImageJ-devel] [fiji-devel] imglib coding style

Curtis Rueden ctrueden at wisc.edu
Wed Apr 14 16:38:33 CDT 2010

Hi Johannes,

I agree that we should pay attention to the coding style of imglib, ImageJ
and related Fiji projects. My current plan for ImageJ is to use Eclipse,
since it allows you to define source code formatting conventions and apply
them. I believe you can also export the rules as XML so that we can commit
them to the git repository. Eventually we could even have a post-commit hook
to take care of it.


On Wed, Apr 14, 2010 at 3:18 PM, Johannes Schindelin <
Johannes.Schindelin at gmx.de> wrote:

> Hi,
> I just tried to come up with a sensible way to ensure that I do not
> violate the coding style of imglib. This is what I came up with (it
> requires version 1.24 of Artistic Style: http://astyle.sourceforge.net/):
> astyle --indent=tab --unpad-paren --pad-paren-in --pad=oper --mode=java
> --keep-one-line-blocks --keep-one-line-statements --suffix=none
> --lineend=linux --formatted $(git ls-files \*.java)
> Many of the files have CR/LF line endings, so if you want to see what this
> _really_ changes, call:
> git diff --ignore-space-at-eol
> In any case, don't do that if you have uncommitted changes you want to
> keep!
> Ciao,
> Johannes
> P.S.: if anybody is interested, I can commit the result to a topic branch.
> --
> You received this message because you are subscribed to the Google Groups
> "Fiji-devel" group.
> To post to this group, send email to fiji-devel at googlegroups.com.
> To unsubscribe from this group, send email to
> fiji-devel+unsubscribe at googlegroups.com<fiji-devel%2Bunsubscribe at googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/fiji-devel?hl=en.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20100414/d7036bd6/attachment.html>

More information about the ImageJ-devel mailing list