M
Marian Edu
Guest
Evan, great initiative... with all those ideas floating around guess will end-up a mix between compiler and tooling features. For me 'strict' means more something like 'all warnings are errors' but then we need to spot the warnings that have the most potential to be actual errors. What I would like to see implemented is more the 'compliance level' so if I need to make sure the code will compile in V9 just set that in project settings... that will ease the pain for some of the ISV's out there. Ah, strict should flag as error all usage of deprecated keywords (tooling support so we can use @deprecated annotation in frameworks will be a nice addition), if you can find possible leaks on memptr/handles (com, sax, sockets) would be great. And while you're at it... something I've loved from Larry's talk about perl 6, aim for awesome error messages 
Guess those are the kind of messages that points to a solution instead of just the error, check-out user reports on 'less than awesome error message'.
Continue reading...
Guess those are the kind of messages that points to a solution instead of just the error, check-out user reports on 'less than awesome error message'.Continue reading...