Now that we have solved one of the major problems--dynamic unicode strings--, seems a good time to reorganize the code.
I have thought about using a single namespace, "Afx", for all the classes, present or future, that comprise the framework. This way, we don't have to remember and type several namespace names, just "USING Afx". It also has the advantage of being short, so if we need to override some calls because of naming conflicts, we just have to type "Afx.".
CWindow will include AfxWin.inc, that in turn will include CBSTR.inc. The other includes can be optional and will require the use of #include once to use them in order to no force the compiler to parse a big amount of code unless needed. Somebody writing a console program does not need to include CWindow.inc or AfxCtl.inc, for example.
If you agree, once organized and completed with some functions that I have been delaying because need to return an unicode string, I will post a further release candidate version for testing and later we can publish it as version 1.0 and archive all these discussions in order to no confusse new users.
What do you think?
Jose,
Sounds good to me.
James
Jose,
Just curious on why you include a var name in your DECLARE's.
James
Hi Jose - I agree 100%. One namespace and easy Include'ing into the main file sounds great. And yes, we'll then clean up all of the old posts regarding the subject as not to confuse anyone browsing the forum.
Quote from: James Fuller on July 13, 2016, 07:39:34 AM
Jose,
Just curious on why you include a var name in your DECLARE's.
James
It takes less time.
I first write the function and then just copy and paste the first line and change private for declare.