What is missing in programming environments
yu Alone Coder
Some programs are written like this. They start by thinking about:
1. first the program does something
2.then this and that
3.then this and that
etc.
I often write all these points in the comments before writing
the code itself. That is, the program is divided into some sections.
Why not highlight them when editing?
Often (especially in assembly language) comments on the right are required,
standing in a column and describing in human language what they are doing,
for example, some three lines. When changing these lines
(for example, the names of the labels in them) it may turn out that
the comment must be moved to the right, all three lines at the same time,
so as not tobreak a column. In no environment known to me is this
provided.
Often you need to mark the date of some change (or version, in
which it appeared). In general, it is not so easy to find which
changes occurred at certain times, even a couple of hours
back. And the environment could store the dates of all changes and, for example,
show them with different background colors. In addition, show a list
changes in chronological order so that you can quickly
find what you need and move the cursor to it.
Half of all nepemotok text when editing the source
occurs with the aim of moving from the body of one function to the body of another.
Delphi allows you to go to the definition of a function whose name is
cursor, but often you need to look at the function whose name is in
there is no nearby area. Alasm allows using the menu Ext+L
move between marks in the current source. But far from it
each editor allows you to open two windows with different locations
the same text. Moreover, in language Pascal functions
represent entities independent from each other, and it is possible
it would be to scroll through them all separately by default (choosing from
list).
Share your thoughts about the article