[Octave-patch-tracker] [patch #9853] [octave forge] (image) implement niftiread, niftiwrite, niftiinfo

[Qianqian Fang]

Follow-up Comment #12, patch #9853 (project octave):

just to let you that I have restarted working on code style reformatting.

the latest version can be found at

https://github.com/NeuroJSON/jnifty/tree/octave9853

the files included are the minimal set as discussed in comment #5, where I
added fopen('z') and removed zmat/jsonlab dependencies (although, if they are
installed, they can also be called).

I am using miss_hit (https://github.com/florianschanda/miss_hit) in the octave
mode (--octave) to do as much automated formatting as possible. To tune the
miss_hit config rules, I would like to get some pointers on the formatting
style

So far, the current miss_hit formatting rules have done the following:

1. set indentation to 2 spaces
2. adding white spaces after comma and around operators

I might have to do some of the remaining formatting manually. Before that, I
want to know the following:

Which of the styles in https://wiki.octave.org/Octave_style_guide are
absolutely required? is endfunction/endif/endfor required? is using '#'
instead of '%' required? if someone can point me to a template file, that
would be very helpful. thanks


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/patch/?9853>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/