[torquedev] Quick test report of cpuset support

Dave Jackson jacksond at clusterresources.com
Sat Feb 16 07:56:33 MST 2008


  My #1 goal with coding style is consistency.  The original OpenPBS code
was developed by a distributed committee and contained numerous coding
styles or lack of coding styles.  It was a mess.  It was difficult to
following, difficult to enhance.  The current coding style particulars
are not absolutely critical but it is simple, straightforward, and
consistent with other products we work on and helps CRI based developers
be more productive.  We are making significant efforts to constantly
clean it up and constantly improve internal documentation and comments
with every project and bug we work on.

  Still, this is a community project and for coding style, it should be
determined by the primary contributors to the code.  What Garrick, Glen,
and other contributors suggest will be weighted very heavily in making a
decision on any changes.  So, I guess, if you want specific changes, let
the lobbying start... :)


> ----- "Garrick Staples" <garrick at usc.edu> wrote:
>> On Sat, Feb 16, 2008 at 04:52:27PM +1100, Chris Samuel alleged:
>> > Out of interest - is it worth running GNU indent over
>> > the Torque code for a consistent layout ?
>> Dave wouldn't like that.  He's a stickler for his style :)
> Problem is that I was only really able to follow what
> was happening in the code once I'd run indent over cpuset.c,
> though that might be more a reflection on the fact that
> I'm a sysadmin, not a programmer. :-)
> cheers,
> Chris
> --
> Christopher Samuel - (03) 9925 4751 - Systems Manager
>  The Victorian Partnership for Advanced Computing
>  P.O. Box 201, Carlton South, VIC 3053, Australia
> VPAC is a not-for-profit Registered Research Agency
> _______________________________________________
> torquedev mailing list
> torquedev at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torquedev

More information about the torquedev mailing list