Difference between revisions of "GlueX Offline Meeting, November 4, 2009"
(→Minutes) |
(→Minutes) |
||
Line 52: | Line 52: | ||
David presented the ???results of his editorial work on the CLEO conventions that we agreed to use as a starting point for our own conventions. We went over on a few items that David, Richard and Elliott flagged as requiring discussion. We came to some conclusions on most of them: | David presented the ???results of his editorial work on the CLEO conventions that we agreed to use as a starting point for our own conventions. We went over on a few items that David, Richard and Elliott flagged as requiring discussion. We came to some conclusions on most of them: | ||
− | drop namespace requirement | + | * drop namespace requirement for variables in a library |
− | drop inline constructor | + | * drop prohibition against inline constructor |
− | + | * "at least one constructor" not "defined default constructor" | |
− | c not k | + | * c not k for constants |
− | + | * lack of virtual destructor causes compiler errors, drop the rule | |
− | !p not that bad | + | * "if (!p)" where p is a pointer, is not that bad |
− | declare | + | * go ahead and declare more than one variable per line |
− | use doxygen style comments | + | * "use doxygen style comments" not "use //" |
− | drop the integer less than greater than thing | + | * drop the integer less than greater than thing for testing intervals |
− | scripts for skeletal template should include link to coding standards | + | * scripts for skeletal template should include link to coding standards[?] |
+ | |||
+ | Alex and Mark asked what constitutes thread safe code. The answer is not simple. | ||
+ | |||
+ | We did not decide what to do from here on this issue. | ||
− | |||
− | |||
==New Action Items== | ==New Action Items== | ||
# Schedule a presentation on OSG from Richard -> Mark | # Schedule a presentation on OSG from Richard -> Mark | ||
+ | # Schudule discussion of a "warning-free code" policy -> Craig |
Revision as of 10:46, 5 November 2009
Contents
Location
The meeting will be at 2:00 pm in CEBAF Center A110
Telephone
To connect by telephone:
- dial:
- 800-377-8846 : US
- 888-276-7715 : Canada
- 302-709-8424 : International
- enter participant code: 77438230# (remember the "#")
Video Conferencing
A) ESNet: 8542553
B) EVO: direct meeting link
Slides
Talks can be deposited in the directory /group/halld/www/halldweb1/html/talks/2009-11
on the JLab CUE (you have to be a member of the "halld" Unix group). This directory is accessible from the web at https://halldweb1.jlab.org/talks/2009-11/ .
Agenda
- Review minutes from last meeting: all
- Announcements
- Meeting time schedule decision
- Hall D Group Membership: Elliott
- GlueX Coding Conventions: David
- Parameterized B-field: David
- Action item review: all
Minutes
JLab: Craig Bookwalter, Mark Ito (chair), David Lawrence, Sascha Somov, Simon Taylor, Aram Teymurazyan, Elliott Wolin, Beni Zihlmann
UConn: Richard Jones
Review of Last Meeting's Minutes
We glanced over the items from the ???Octember 99??? meeting. No additional discussion was generated.
Announcements
Meeting Time: We looked at the scheduler and settled on Tuesday at 2:00 pm as a suitable time for regular bi-weekly meetings. The next offline meeting will therefore be on Tuesday, November 17.
Hall D Group Membership
Elliott led us through the ???list of members of the "halld" Unix group at JLab. IT Division has suggested that we review the list and drop those users who do not need the associated privileges. Elliott will drop the obvious candidates from the list.
GlueX Coding Conventions
David presented the ???results of his editorial work on the CLEO conventions that we agreed to use as a starting point for our own conventions. We went over on a few items that David, Richard and Elliott flagged as requiring discussion. We came to some conclusions on most of them:
- drop namespace requirement for variables in a library
- drop prohibition against inline constructor
- "at least one constructor" not "defined default constructor"
- c not k for constants
- lack of virtual destructor causes compiler errors, drop the rule
- "if (!p)" where p is a pointer, is not that bad
- go ahead and declare more than one variable per line
- "use doxygen style comments" not "use //"
- drop the integer less than greater than thing for testing intervals
- scripts for skeletal template should include link to coding standards[?]
Alex and Mark asked what constitutes thread safe code. The answer is not simple.
We did not decide what to do from here on this issue.
New Action Items
- Schedule a presentation on OSG from Richard -> Mark
- Schudule discussion of a "warning-free code" policy -> Craig