Deletions are marked like this. | Additions are marked like this. |
Line 26: | Line 26: |
* Pretty printing source code from Linux: enscript -r -2 -C -Ecpp <filename> | * Pretty printing source code from Linux: enscript -r -2 -C -E<language> -P <printer> <filename>, where language is c or cpp, printer is the name of your printer as you would pass it to lpr, and filename is the .c or .cpp file. This will queue the file to the printer. |
Martinos Dev Meetings Topics
This is a list of future Martinos Dev meeting topics. Martinos Dev meets at 2pm on Wednesdays in the CSRL meeting room in Building 149. Please add requests or volunteer to present your own topics.
Upcoming Topics
10/26: JoshSnyder - Code review.
11/2: NickSchmansky - Use of splint to verify and standardize code.
11/9: DennisJen - Comparison of IDEs and/or project management tools.
- 11/16:
Reserve Topics
Topics which can be used if a scheduled speaker becomes unavailable.
DavidTuch - Interruption management, ie, how to create uninterrupted blocks of time.
Requests
using Doxygen, http://www.stack.nl/~dimitri/doxygen/ (nick)
applying Knowledge Management tools to extract an ontology from the Freesurfer mailing list (to categorize emails), discuss these topics: http://www.searchtools.com/info/classifiers.html (nick)
Resources from past meetings
Code Review
[http://www.processimpact.com/articles/inspects.html Process]
Pretty printing source code from Linux: enscript -r -2 -C -E<language> -P <printer> <filename>, where language is c or cpp, printer is the name of your printer as you would pass it to lpr, and filename is the .c or .cpp file. This will queue the file to the printer.
In-house Code
RudolphPienaar has put together a [http://www.nmr.mgh.harvard.edu/~rudolph/software/toolsAndUtilities/internal/internal.html page] to keep track of code developers have available for in-house use. Please feel free to email him to contribute your own code.