C/C++ files with "Ex" suffixes
-
I noticed in the microsoft windows library they had two versions of what i assumed with similar files. filename.h/filename.cpp and filenameEx.h/filenameEx.cpp Anyone know how this "Ex" suffix is used? and what the relationship if any between the non-Ex and the "Ex" version? Kind regards, David
-
I noticed in the microsoft windows library they had two versions of what i assumed with similar files. filename.h/filename.cpp and filenameEx.h/filenameEx.cpp Anyone know how this "Ex" suffix is used? and what the relationship if any between the non-Ex and the "Ex" version? Kind regards, David
it really depends on the company/implementation - I doubt there's any 'standard' meaning, eg 'Example', 'Extension' - the only way to know for sure is a side-by-side comparison using [insert name of your favourite diff/compare tool here]
-
I noticed in the microsoft windows library they had two versions of what i assumed with similar files. filename.h/filename.cpp and filenameEx.h/filenameEx.cpp Anyone know how this "Ex" suffix is used? and what the relationship if any between the non-Ex and the "Ex" version? Kind regards, David
david21742 wrote:
Anyone know how this "Ex" suffix is used? and what the relationship if any between the non-Ex and the "Ex" version?
I always interpreted it as an "extended" version.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
-
I noticed in the microsoft windows library they had two versions of what i assumed with similar files. filename.h/filename.cpp and filenameEx.h/filenameEx.cpp Anyone know how this "Ex" suffix is used? and what the relationship if any between the non-Ex and the "Ex" version? Kind regards, David
Basically it stands for an extended version. Microsoft follows 2 conventions for extensions or newer versions of files / APIs / classes. MFC has a
CDialogclass which is now extended toCDialogEx.CDialogExexists in a file calledAfxDialogEx.hThere are several extended versions of APIs that follow this convention -CreateWindow-CreateWindowExRegOpenKey-RegOpenKeyExThe other convention that is followed is to add the numbers 2, 3, 4 ... to the end of the name. Files that follow this convention are -AfxPriv.h,AfxPriv2.hAfxCmn.inl,AfxCmn2.inl,AfxCmn3.inlThis convention is followed by the COM interfaces -IClassFactory,IClassFactory2IPersistFolder,IPersistFolder2,IPersistFolder3«_Superman_» _I love work. It gives me something to do between weekends.
_Microsoft MVP (Visual C++) (October 2009 - September 2013)
-
Basically it stands for an extended version. Microsoft follows 2 conventions for extensions or newer versions of files / APIs / classes. MFC has a
CDialogclass which is now extended toCDialogEx.CDialogExexists in a file calledAfxDialogEx.hThere are several extended versions of APIs that follow this convention -CreateWindow-CreateWindowExRegOpenKey-RegOpenKeyExThe other convention that is followed is to add the numbers 2, 3, 4 ... to the end of the name. Files that follow this convention are -AfxPriv.h,AfxPriv2.hAfxCmn.inl,AfxCmn2.inl,AfxCmn3.inlThis convention is followed by the COM interfaces -IClassFactory,IClassFactory2IPersistFolder,IPersistFolder2,IPersistFolder3«_Superman_» _I love work. It gives me something to do between weekends.
_Microsoft MVP (Visual C++) (October 2009 - September 2013)
thank you very much. i had to name something where it was in appropriate to overload, and I couldn't think of an appropriate name. i saw something in microsoft's thread or mutex library that used that naming convention. I should have realized Ex meant "extended", duh. Kind regards, :java: