> > I think it's a drop in the bucket compare to new features we're adding > plenty of on every version. These make the language a lot more complex > than var being an alias to public (not even different syntax). >
Very true. I'm not proposing this because it's a great new feature. But has this legacy functionality outlived its original purpose? If so, maybe it's time to start phasing it out. Sure, it's a small drop in the bucket of improvements, but it's still a drop nonetheless. To me, var falls squarely in the bucket of "no strong reason to remove". > I agree 100%. But is there a strong reason to keep it forever, especially considering its decline in usage? Perhaps by targeting it for removal in 8.0 we can mitigate the impact of such a BC break while taking one small step in improving the language over time. Colin