Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Debug inside inl (inline files)

(1/2) > >>

mushakk:
Many people (like me) separates declaration from definition in all classes. For templates normally we use the .inl extensión.

Please permit debug inside .inl files.

Thanks for your work.

DrewBoo:

--- Quote from: mushakk on March 03, 2008, 09:10:17 pm ---Many people (like me) separates declaration from definition in all classes. For templates normally we use the .inl extensión.

Please permit debug inside .inl files.

Thanks for your work.

--- End quote ---

I also have used .inl on some projects.

Are there any plans to allow the end user to outright specify what extensions are valid for certain file types and expose that list in the SDK?

MortenMacFly:
Mind providing a little sample project? I'm under the assumption this should be possible...

DrewBoo:

--- Quote from: MortenMacFly on March 12, 2008, 08:38:35 pm ---Mind providing a little sample project? I'm under the assumption this should be possible...

--- End quote ---

Morten, you're everywhere.   :lol:

.inl is synonymous for .h or .hpp for many people.  It's just another extension for a file that gets #included.

I've also worked on projects where ".C" and ".H" files were used (instead of lower-case).  I had to modify several core files on my local machine to hack that functionality in, which is why it may prove Useful Enough(TM) to have C::B let the end user modify which files extensions are considered C++ source, C++ headers, etc.

MortenMacFly:

--- Quote from: DrewBoo on March 12, 2008, 08:49:54 pm ---which is why it may prove Useful Enough(TM) to have C::B let the end user modify which files extensions are considered C++ source, C++ headers, etc.

--- End quote ---
Well... did you ever try righ-clicking on a project and then select "Project Tree" -> "Edit file types and categories"???

Navigation

[0] Message Index

[#] Next page