[Ovmsdev] Source Code Formatting

Michael Balzer dexter at expeedo.de
Fri Mar 25 03:53:44 HKT 2016


I'm afraid the mix of code styles is my fault... there are still parts
in the framework I've done in my style, and my style is not always
consistent as well.

I configured my MPLAB options to get the default style but also
occasionally forgot to reformat my work before committing.

I've attached my formatting options export from MPLAB IDE, should be
importable directly. Please check if you can use this.


Am 20.03.2016 um 02:55 schrieb Tom Parker:
> Hi,
> I've made a few improvements to the nissan leaf code (see
> https://carrott.org/git/Open-Vehicle-Monitoring-System.git/log/refs/heads/nissan-leaf
> and the climate control branch on the same server ) and I noticed it
> had a mix of code styles. I'd like to reformat it to be consistent
> (mostly because I can't write consistently formatted code without a
> code formatter) and wanted to know if there is an agreed format to use
> -- there is nothing worse than trying to trace changes through a code
> formatting war in the history?
> I'm currently using the default mplabx code format configuration which
> suits me but is different from most of the rest of the OVMS code. Is
> there a configuration for mplabx I can import?

Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mplab-formatting.zip
Type: application/zip
Size: 1076 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160324/f163f94b/attachment-0002.zip>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dexter.vcf
Type: text/x-vcard
Size: 206 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160324/f163f94b/attachment-0002.vcf>

More information about the OvmsDev mailing list