Talk:Insight Segmentation and Registration Toolkit
This is the talk page for discussing improvements to the Insight Segmentation and Registration Toolkit article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Untitled
editI'm trying to clean up this page in order to meet the Wikipedia standards. I see that the page has been tagged for cleanup since january 2007, but I would like to get some guidance on how to proceed with the cleanup.
In the meantime I'm mostly copying the style of the Qt Toolkit page, that I assume should be a good model for ITK.
Please advice.
LuisIbanez 20:09, 24 February 2007 (UTC)
"Such C++ templating means that the code is highly efficient, and that many software problems are discovered at compile-time, rather than at run-time during program execution."
I don't see much proof for that. Do they provides some hard number on that ? It sounds to me that it only generates big cache-missing libraries and bloated bindings. If there is some benchmarks, it should be referenced in the article.
- The claims about the effects of "C++ templating" are unsupported and should be removed.Truprint (talk) 18:47, 29 October 2009 (UTC)