What if there was a NEW vb6

[FunkyDexter]

Olaf, my point was that I don't believe the project you were proposing will meet AxisDJ's requirements. Perhaps I've misunderstood your proposal and perhaps not so to remove doubt lets get down to the actual user requirement. AxisDJ's kick starter contains the following:-

It will only succeed if at least 99% of the vb6 code is importable and a programmer can import his/her vb6 project and re-compile it in a few hours.

So the question is: will your proposed solution allow the import of a complete VB6 project, replete with forms, user controls, frm and frx files, code behind, and third party components (.dlls, .coms ActiveX etc, both compiled and as source) and "just work" on a simple recompile?

If the answer to that question is an unqualified "yes", then I take it back, you have the potential to close a wide gap that a lot of people clearly want closed. If you need to qualify that "Yes" in anyway then that's a real danger sign that the your proposal and AxisDJ's requirement don't truly marry up. If my reading of your comment in that thread is correct (and it may not be) you were saying that at least one of those elements won't be supported. Indeed, you've already got a qualification in your post in this thread: "My priority for the compiler would be 1:1 Code-compatiblity (as well as Type-compatibility with regards to SafeArrays, Variants, (V)BStrings etc.) when importing and compiling *.cls and *.bas modules only."

AxisDJ is talking about giving $150, 000 dollars of other people's money. Before that happens you both have a moral responsibility to put any gaps between their expectations and what you propose to deliver right up front. Don't get bogged down in justifying your approach or explaining why those gaps are necessary or unavoidable, just show them the gaps in plain and simple terms.