Thank you SioSio.
I apologize for thinking that some might not know the following. Please forgive me, but such a reply of VS code and further statements seem to indicate that still some people do not know some things. I do not know C++11, and I understand not knowing. I will try to be gentle and conversational in my explaining some of this.
If I recall correctly, VB6 begins with a single code page for the programmer, and then converts all input code (internally) to Unicode, and then does all of it's internal work in Unicode, and then converts all responses to be given and shown to the user into the user's (previously detailed) single code page. I think that your Boolean of "nobody would have made" might be based upon not understanding the mechanics of the VB6 platform. VB6 is an extremely powerful system built by Microsoft that, for the most part simply automated the GUI process for the user and allowed the user to concentrate on the logic code.
It is possible and I have seen bits of code that list both vb6 and C++. In the past, I used to study the comparisons and try to learn some tiny amount of C++ from the comparisons.
Sometimes (when I used VB6) I injected C++ code into my own VB6 programs and it worked. VB6 is like a front end that pre-wrote lots of stuff, similar to how wxWidgets does with C++ now. Similar, but hidden from the programmer while it is internally in Unicode and the user is limited to one chosen code page. I think that wxWidgets is a current attempt by others to emulate VB6. I have used wxWidgets for C++ and it is similar to VB6 except that VB6 is very intuitive and smoothly usable. I have since dumped wxWidgets and went directly to learning C++.
The readers of this post should already know this stuff, but some are new to so much that they need a historical explanation of why this question is even being asked. The following may help them:
I think that the reason that Microsoft has pushed so aggressively to convince the generally limited intellects to be hateful of VB6, is because VB6 is so powerful that it is out of Microsoft's control. Kind of like Microsoft came up with ".net" to break the (to some) mind-bending complexity and unmitigatedly secure C++ of Bjarne Stroustrup. Stroustrup's genius seems to have bypassed the armies of Microsoft programmers so completely that Microsoft came up with a way to break into the C++ code in transport from computer to computer via a so-called "JIT Just In Time" compilation that sent the code in raw form that they could read and change as they decided via the end chain compiler. Stroustrup's C++ never needed that. It is like the Finale to Beethoven's 5th Symphony. C++ never needed help from any JIT compiler. Never... Ok... Now back to VB6... Previously, it seems that for VB6, Microsoft could not stop the vast new programs being created rapidly in VB6 (sp5), thus they lost control of the volumes of new programs and thus Microsoft drove the witless to hate it. Microsoft programmed VB6 so well that the untrained average person could quickly learn to use it and produce advanced controls for industry. Those controls (programmed by common VB6 users) were so advanced that Microsoft had difficulty in competing with them. Microsoft seems to have successfully locked itself out of many software markets. Microsoft did well with VB6. Microsoft seems to have outdone themselves. They had given away the ability to program to the masses and they might have regretted that severely! But, then they learned that they had so enabled the average person to rapidly produce software that Microsoft had no control over them. I expect that Microsoft did not make a single penny off of most of those new programs. What a loss of potential revenue! Then, grasping their monumental mistake, it looks like Microsoft attempted to flood the internet with illogical noise proclaiming that the masses should and do hate VB6. Outside of themselves of course: Secretly Microsoft themselves still use VB6 in Microsoft Office in a stripped down version called "VBA." Ok. So now you know some of the value of VB6(sp5). Do not use Service Pack 6 (sp6). No matter what you read elsewhere about the "necessity" and "praise" of service pack 6, stay away from it. Do not even allow a CD containing it in your building. Do not make the mistake of using sp6. Stay with VB6 and service pack 5. Now you might understand why there are still possibly millions of people programming in VB6(sp5) and why those people will probably never leave it. And, now you might understand that a converter from VB6(sp5) to any version of C++ has been in demand for many years.
It can be made. I have seen attempts to make it. It will never be made with any ".net" language partially because ".net" is not C++. And, if you see a converter that goes from VB6 to C++.net, then it is *not* to C++, it is to some version of the anti-security ".net" and it is not C++.
Now I am studying C++. I have some vast programs that I programmed in VB6 (sp5) that I would like to have converted to C++ easily.
This topic has been discussed many times, years ago. I want an update on if the conversion has been completed. If it has, then where can I get it? I have not found a suitable process on the search engines yet. Most attempts converted to ".net" which is worthless (to me), and ".net" is now hopefully a dying anti-language. I am looking for conversion between VB6 (sp5) and C++ (any version up to and including 11).
Thank you.
| 
