posted 19 years ago
I think allowing static local variables in methods would have been a good idea. When you need the methods to remember their instance-independent state between calls.
I know, I know... you can still maintain this state information with static class variables but the idea is to have maximum encapsulation possible (if a member variable is only used to keep the state information about a single method, why expose it to the rest of the class).
I'm not too bothered about not having them though.
-- SCJP 1.4 (98%), SCJD (98%), SCWCD (96%), OCA Dev (97% avg.), SCBCD (97%), SCJP 1.5 BETA (90%)<br />-- OCP Dev (maybe), MCDBA (probably) SCEA (eventually)<br />-- Haven't tried Firefox yet? Free, open, secure, fast, tabified, and slick!<br />-- <a href="http://www.mozilla.org/products/firefox/" target="_blank" rel="nofollow">http://www.mozilla.org/products/firefox/</a>