Writing code for a reader

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #56613
    Support
    Keymaster

    I'm sorry, I didn't think this code is incomprehensible…

    Code is not only smaller, all repeated code is contained in one procedure, it's more handy for changing or for debug for me.

    And very handy for adding of new properties (part of a code exists already).

    Do you mean, indexing of properties with equal setters or getters is a bad idea? Why this code is not incomprehensible?

    #56620
    HeDiBo
    Participant
    'Support' wrote:

    Do you mean, indexing of properties with equal setters or getters is a bad idea? Why this code is not incomprehensible?

    Maybe if the index would have symbolic names, it would be better.

    But this was only an example.

    In general the code should be so easy to read, that a manual would be superfluous. That would accomplish two things: a very maintainable source code and a very good reference text for your users. As it is now, all efforts are made to shrink the source code. I even saw this in the transition of 12.06 to 12.07:

    Code:
    .
    .
    else
    inherited;
    .
    .

    was changed into

    Code:
    .
    .
    else inherited;
    .
    .

    Why? Do you really think the latter is more readable? I give it to you that readability of the source code was never a goal. However, my many years of experience taught me that readability is the prerequisite for maintainability.

    Don't get me wrong. I love AC. It's because I want it to be most successful that I take the time for such critics.

    Keep up the good work a7.gif

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.