[torquedev] Changes to Formatting in TORQUE 2.3 and 2.4

Garrick garrick at usc.edu
Fri Sep 5 17:34:54 MDT 2008

Note the reason why this wasn't done a long time ago was because  
coding style was a useful way to determine if code was unchanged from  
the original openpbs code.  At a glance, anyone immediately knew if  
someone had "touched" a given section of code.

HPCC/Linux Systems Admin

On Sep 5, 2008, at 12:52 PM, Matti Bickel <cat5 at minet.uni-jena.de>  

> Josh Butikofer <josh at clusterresources.com> wrote:
>> Our objectives in picking a format style were:
>> * The style would be consistent throughout the TORQUE code. This is  
>> the
>> biggest gain.
> Yes, yes, yes! Thanks a lot for this move. I'm happy with almost any
> coding standard, as long as it's uniformly applied to the code.
>> astyle -s2  -b --indent=spaces=2 -S  -B --convert-tabs
>> --indent-preprocessor --break-blocks
>> --pad=oper --unpad=paren --mode=c <FILENAMES>
> I try to apply this style to the ipv6 branch as well.
> -- 
> Regards, Matti Bickel
> Signed/Encrypted email preferred (key 4849EC6C)
> _______________________________________________
> torquedev mailing list
> torquedev at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torquedev

More information about the torquedev mailing list