Re: Is Smart Eiffel ready for large-scale application ? (Modula 3 and Eiffel verbosity and libraries)
Mike Meyer <[email protected]>
| Newsgroups | gmane.comp.lang.eiffel.smalleiffel |
|---|---|
| Message-ID | <[email protected]> |
In <[email protected]>, Dominique Colnet <[email protected]> typed: > > they prevent seeing more contents at once. In other words: less is more! > But, just forget your code for about 6 months (i.e. take some very long > vacations ;-)... and the long name `get_new_iterator_on_keys' will be > better than the short hand I think. I don't. I've used languages where the method is "keys", and have no trouble remembering it. Then again, it's in a standard data structure of the language, so it's not dependent on the program. Longer names are more usefull for application-specific methods, but even then it behooves one to follow the library. If the library calls the method that returns an iterator on the keys of a mapping "keys", then your application-specific object that does the same should be called "keys", not "get_new_iterator_on_keys". Of course, the converse is also true. <mike -- Mike Meyer <[email protected]> http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.