Eelco, The only purpose of this test was to make sure that no one building Wicket from CVS is using a compiler with that bug. It not only proves that JDK 1.5 is used for testing, but also that class file generated don't contain the bug. I haven't checked the whole Wicket code for such a construct, but as we are using final quite a lot, it may very well be. And if not now, it may be in the future. It is just like fuse, going off if the environment is wrong. Doesn't that help prevent strange error messages and people wasting time while hunting a potential problem? I still think is makes sense.
Regards Juergen -----Urspr�ngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Eelco Hillenius Gesendet: Dienstag, 9. November 2004 18:58 An: Wicket Developer List Betreff: [Wicket-develop] FinalTernaryIfCompilerBug I do not agree with the test case 'FinalTernaryIfCompilerBug'. I read about the bug, but as this construction is never used (yet?) in Wicket, this is never a problem. Furthermore, if the test failes, it only proves that JDK 1.5 is used for testing. I'll remove the test class. Anyone disagrees with this? Eelco ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Wicket-develop mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wicket-develop ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click _______________________________________________ Wicket-develop mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wicket-develop
