Content deleted Content added
→Possible Fallacy in Feature comparison: just keywords? |
|||
Line 375:
::::::: I must disagree about AWT event handling. You can't do ANY event handling on GUI components in java without using AWT event handling (or it will be VERY hard), because it's hard wired into the language. You can get rid of the AWT components, but not events (and not graphics either). There are two parts of AWT, which people may find confusing: the "core" part, which interface with the native event handling, graphics, and windowing system. And the AWT components. Your WPF and WinForms comparison is valid only for the latter part. [[User:Hervegirod|Hervegirod]] ([[User talk:Hervegirod|talk]]) 17:55, 5 December 2010 (UTC)
:::Java does not have events as a first class feature, and not as a language feature. Period. If you consider java.util then yes, there is a conventional way to ''implement'' events. However, AWT has no place in this article. AWT is a framework built ''using'' the language, in no way can it be presented as part of the language or even the core library. Events are defined in java.util and if this article should allow "core" libraries then Java+core library can be said to feature events. [[User:Useerup|Useerup]] ([[User talk:Useerup|talk]]) 15:22, 6 December 2010 (UTC)
::::So, it's just the reserved keywords, then? --[[User:Nigelj|Nigelj]] ([[User talk:Nigelj|talk]]) 19:55, 6 December 2010 (UTC)
| |||