Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: DrewBoo on March 25, 2008, 05:06:09 pm

Title: Conflicting meaning of "source" and "header"
Post by: DrewBoo on March 25, 2008, 05:06:09 pm

Code::Blocks seems to have two different concepts of what "source" and "header" files are.

Is there a plan to unify these?

Namely, the project manager understands "file types & categories", using a user-defined set of masks with wildcards.  By default, it specifies particular extensions but the interface looks like it would allow any wildcard mask, such as "prefix*.*".  And out of the box, the project manager is aware of files that are "headers" and files that are "sources".

Elsewhere, there are hard-coded extensions in the C::B source that specify exactly what file extensions count as "header" and "source".  An example is "Swap header/source (F11)" in the edit menu, which does not know what the project manager thinks "headers" and "sources" are.


If there's a rough plan to unify these but it's sitting on the back burner, I'd be happy to cook up  some minimal patches and lob them over here.

Title: Re: Conflicting meaning of "source" and "header"
Post by: DrewBoo on March 26, 2008, 12:02:13 am

Hm... no opinions from anyone?

I don't usually work with non-standard file extensions, but when I must (currently, .C and .H capitalized) many features break, even though C::B acts like it can handle it.

Should I just submit some reports to berlios?  Patch it myself and share the changes?

Title: Re: Conflicting meaning of "source" and "header"
Post by: mandrav on March 26, 2008, 08:33:31 am

Yes, this will change eventually although it's not top priority.

Title: Re: Conflicting meaning of "source" and "header"
Post by: joubertdj on March 26, 2008, 11:42:46 am

Quote from: DrewBoo on March 26, 2008, 12:02:13 am

Should I just submit some reports to berlios?  Patch it myself and share the changes?

I would go this route. It may/may not actually be included in the SVN. If it doesn't break any plugins or C::B for that matter it will most probably be included if it is a desired feature! In other words... GO FOR IT !!!