.inl file extension... What are the gcc alternatives?

[FocusedWolf]

i need a solution that works in vs.net to...

Over there i did what others suggested and used a .inl file format, to hold the implementation of a templated class...where at the bottom of that classes header file i #include the .inl, so the templated class compiles right.

.cpp and .cxx don't work because vs.net, and probably codeblocks to, tries to compile them (if anyone knows some #define trick to make the compiler skip the code at the right time so i can keep the implementation in a .cpp file, please let me know), resulting in a bunch of errors.

.hxx is a potential solution (better then .h implementation in one header file, and declaration in another header file is kinda conussing), that seems to be ok, but i'm just wondering if this is "ok", and not against some cosmic c++ lay about where function implementations should not go?  :lol:

[mandrav]

Two options:

1) You can still use .inl. Did you try and faced problems?
2) You can disable the .cpp file from compiling and linking.

[FocusedWolf]

i think my code had other reasons for not compiling, but i just would like .inl to fall under the source folder and not the "others" folder :p

[mandrav]

i think my code had other reasons for not compiling, but i just would like .inl to fall under the source folder and not the "others" folder :p

Golden Tip Of The Day:
Go to "Project->Project tree->Edit file types & categories" and add "*.inl;*.INL" (without quotes) in the sources mask

[FocusedWolf]

Thx that worked out