Skip to content

agenda call 2015 05 07

nmrcardoso edited this page May 6, 2015 · 9 revisions

Developer call 2015-05-07

  1. Development updates - part I

  2. Code style (Nuno) Purpose: Have the same style without loosing time learning/applying it.

    • Automatic code formatter:
    • Tools that can use this:
      • UniversalIdentGUI (linux, mac, win), http://universalindent.sourceforge.net/ » Supports all the above Automatic code beautifier's and others as well as other languages besides C/C++ » easy to create a configurable file to a specific automatic code beautifier. » live preview » probably the best way to help create a configurable file
      • Atom, https://atom.io/, » packages:
      • atom-beautify -> uses uncrustify code beautifier needs to configure the path and file with uncrustify configurations
      • linter-cpplint -> highlights code that not fits the standards
      • linter-flake -> to remove warning about max line length, change in settings
      • apply style: ctrl+alt+b (to selected code or to all code if there if no code selected code)
      • SublimeLinter, highlight code with incorrect format
        • SublimeAStyleFormatter, uses astyle code beautifier
      • Eclipse/Nsight: » supports K&R, BSD/Allman, GNU, Whitesmiths » allow to load and save configuration style files, xml files
      • other tools?
    • Therefore we can create a configurable file and a simple script to apply the style before uploading code to git.
  3. Automated Testing (move to next call)

Clone this wiki locally