3 ms·
On the other side the reason VB.net broke backward compatibility was to correct things that were obviously bad design decisions in VB6. Like parameters being by
by cm2187 7y ago
On the other side the reason VB.net broke backward compatibility was to correct things that were obviously bad design decisions in VB6. Like parameters being byref by default, having to use the Set keyword for objects, inconsistent 0 or 1 based collection structures, etc.
If VB was meant to survive and move the XXI century, these things had to be fixed.
- orthoxerox 7y agoVB.NET half-broke the compatibility, which got it stuck in the weird space where automatic translation from VB6 was no longer possible, but VB still had lots of quirks that made it harder to coevolve it with C#.