[Insight-developers] ITK convention between #include "" and #include <>

Bill Lorensen bill.lorensen at gmail.com
Fri Jun 25 18:29:12 EDT 2010


Sean,

You may want to hold off for a week. There is a big meeting in
Bethesda this week for ITK's 10 anniversary and a kick off for itk v4.

Bill

On Fri, Jun 25, 2010 at 5:20 PM, Sean McBride <sean at rogue-research.com> wrote:
> Karthik,
>
> Well, I have used the power of grep to change ~700 #include <itk...> to
> #include "itk..." the only ones I didn't change are #include <itksys...>
> which I will leave alone.
>
> I've done this in a clean working copy, and will try building it with
> various build options before committing.  It's a rather scary number of
> changed files. :)
>
> Sean
>
>
>
> On Thu, 24 Jun 2010 08:36:42 +0530, Karthik Krishnan said:
>
>>Indeed, it does appear to be done with both conventions, more so with "<".
>>I'm really not sure.
>>
>>  grep -R "include *<itksys" . | wc -l && grep -R "include *\"itksys" . | wc
>>-l
>>
>>      72
>>      14
>>
>>
>>On Wed, Jun 23, 2010 at 7:43 PM, Sean McBride <sean at rogue-research.com>wrote:
>>
>>> On Wed, 23 Jun 2010 12:07:59 +0530, Karthik Krishnan said:
>>>
>>> >In general its, <> for system includes (STL etc) and " for the others.
>>>
>>> Karthik,
>>>
>>> Does itksys count as a 'system include'?  Mostly seems to be done with
>>> <> but sometimes "".
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.html
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers
>


More information about the Insight-developers mailing list