Minutes 042106: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
| Line 13: | Line 13: | ||
* Some concerns about the burden of explicit instantiation for developers | * Some concerns about the burden of explicit instantiation for developers | ||
** Similar to the wrapping process. Types should be choosen for every class. | ** Similar to the wrapping process. Types should be choosen for every class. | ||
** One file per type. e.g. Image char 3, is one file, Image float 2 is another file. | |||
** How to ensure that future developers will remember to add the explicit instantiation file for new classes ? | ** How to ensure that future developers will remember to add the explicit instantiation file for new classes ? | ||
** How to allow users to turn on selective pieces of the explicit instantiation | |||
** Could it be possible to generate the files instead of having to put them in CVS ? | |||
=== Action Items === | === Action Items === | ||
Revision as of 17:17, 21 April 2006
Attendees
- Bill Lorensen
- Julien Jomier
- Luis Ibanez
- Vincent Magnotta
- Lydia Ng
Discussions
- Borland compiler still have problems with concept checking
- Some concerns about the burden of explicit instantiation for developers
- Similar to the wrapping process. Types should be choosen for every class.
- One file per type. e.g. Image char 3, is one file, Image float 2 is another file.
- How to ensure that future developers will remember to add the explicit instantiation file for new classes ?
- How to allow users to turn on selective pieces of the explicit instantiation
- Could it be possible to generate the files instead of having to put them in CVS ?
Action Items
- Luis: turn off concept checking for Borland in CMakeLists.txt file.
- Julien & Brad to set up a Wiki proposal page on the explicit instantiation
