SourceLinesAndDocu

From Java4c

Revision as of 19:41, 18 July 2011 (view source) Admin (Talk | contribs) (Advantage of textual source lines in comparison with graphic programming - some ideas.) ← Older edit

Revision as of 20:27, 19 July 2011 (view source) Admin (Talk | contribs) m (Protected "SourceLinesAndDocu" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))) Newer edit →

---

Revision as of 20:27, 19 July 2011

Navigation

• up: Main_Page
• down basics: TODO

Overview

Lines of code are many lines - only the developer of them looks through it. Or?

Sources have a structure. It is the formal syntax of the language primary. Code lines are to-down structures of classes, structs, methods, statement blocks. They can be analyzed formally and presented in there structure. Modern programming environments do so.

Advantage of textual source lines in comparison with graphic programming

• Code lines - change tracking: Older and newer versions of sources are able to compare. All source version systems support that. It is possible to track which functionality is changed why, when, who and what exactly.

• Graphical programming - change tracking': If there is a textual representation of the graphical appearance, it is possible to track changes line code lines too. Only it is another notation. But some graphic programming systems stores there content in special maybe binary files or a database adequate form, which doesn't allow a simple comparison of content.

• Code lines - searching anything: Because they are textual files, a grep or ordinary search of text can be applied. Sometimes any textual hint is given to search the proper line. For example there is a textual sequence in an error message or a label on a button - search it in code lines of all files and you find the line where it is handled, without knowledge and understanding of the whole structure of the software.

• Graphical programming - searching anything': It may be a search function in the graphical programming environment. Is it proper to use?

Summary: Code lines are better to handle but graphic programming is better to understand. Use a graphical programming environment with a simple representation of its content in code lines.