Quote Originally Posted by vbrad View Post
As someone who's been wishing for a vb6 upgrade/replacement for well over a decade (not far off two actually) I really wish discussions about desired new features would just go away.
Until twinbasic can open all existing vb6 projects it's no more interesting to someone invested in vb6 than any other language.
I'm contributing to twinbasic, albeit only financially, but I'd prefer if people would leave Wayne to get on with the great job he's doing.
Once compatibility is achieved that's the time to start adding all the new goodies.
Wayne already ready made it very clear that new features must be considered up front. If it's put off for later, it may be far more difficult to implement them. Here is the post. More specifically he said:-
Quote Originally Posted by WaynePhillipsEA View Post
Many will argue that you can add new features later, but I can assure you: it's just not that easy! The codebase for a compiler like twinBASIC is massive and complex; if you don't plan for features up-front at the start, the work to add them later is MUCH more involved (to the point where some new features might not even be possible without re-writing significant parts of the compiler). With tB, a huge amount of effort has gone into designing an efficient and extensible compiler that has the capability to offer any of the features of more modern languages... if and when necessary.
There is no getting away from this.