Re: Is Smart Eiffel ready for large-scale application ? (Modula 3 and Eiffel verbosity and libraries)

Wolfgang Jansen a écrit :

> Joseph Kiniry wrote:
>
>>>> - Eiffel is very verbose. I found myself always putting as much
>>>>   functionallity into one class to avoid the handling of 100 files,
>>>>   for compiler and editor performance. Java has the same problem so
>>>>   maybe this is not a problem for you.
>>>
>>>
>>>
>>> The verbosity is what really gets to me.  Same in Modula-3, which I've
>>> had extensive experience with.
>>
>>
>>
>> The same holds in any language that focuses on readability over 
>> terseness and has types and variable declarations.  It is a simple 
>> fact of language design.
>>
>>> Why is it that every object-oriented language is so wordy?  Java 
>>> escapes
>>> the long-keywords plague, but uses long standard-library names instead.
>>
>>
>>
>> Why is it that people would always trade a few characters for less 
>> intelligible code?
>
>
> I think because fewer character make texts more intelligible!
> You may this observe in natural languages as well as in artificial 
> languages
> as mathematical and chemical formulas. When some new thing (or 
> process, situation ...)
> has to be expressed in a language it will be expressed rather wordy.
> When it is no longer new and has often to be expressed then the 
> expression
> will be soon reduced to a bar minimum. So, an Eiffel feature name like
> `get_new_iterator_on_keys' is very nice when it is newly introduced in 
> a library,
> or used for the first time by a newcomer. After some time one would be
> satisfied with `key_iterator' or even `keys'. Most characters of the 
> original
> long name are redundant for no gain, instead they are disturbing because
> they prevent seeing more contents at once. In other words: less is more!
>
> (OK, this comment is a side step of this discussion thread's topic.)
>
> WJ

yesssssssssss

and if shannon is right it should happen for frequently used feature

jb