G
Guest
Hi,
In a C++/CLR Windows Forms app I notice that there is only a header and no
..cpp for the form. Also event handler bodies are added by the IDE right to
the header.
What is the philosophy on this?
1. Are C++ and/or C++/CLR classes now intended to be typically implemented
in the header?
2. Is this only for GUI and related?
3. Will functions be inlined by default?
4. Any issues with using a header for derived classes? What about exposing
potential IP functionality beyond just prototypes? Is the idea that for C++
with .NET that assembly references/namespaces will be used to expose class
members to clients i.e. headers no longer the primary means of class member
exposure for C++ using .NET Framework?
5. Any recommendations about function bodies in headers?
Thank You
In a C++/CLR Windows Forms app I notice that there is only a header and no
..cpp for the form. Also event handler bodies are added by the IDE right to
the header.
What is the philosophy on this?
1. Are C++ and/or C++/CLR classes now intended to be typically implemented
in the header?
2. Is this only for GUI and related?
3. Will functions be inlined by default?
4. Any issues with using a header for derived classes? What about exposing
potential IP functionality beyond just prototypes? Is the idea that for C++
with .NET that assembly references/namespaces will be used to expose class
members to clients i.e. headers no longer the primary means of class member
exposure for C++ using .NET Framework?
5. Any recommendations about function bodies in headers?
Thank You