Quote:
Originally Posted by tompe
But just describing the intention is not pseudo code. Pseudo code as I understand it is for describing what the actual implementation do and often describe before you implement.
The problem with this kind of pseudo code is that you have duplicated the information. If there is a mismatch you do not know if the pseudo code or the code is correct if both are working according to the interface specification.
|
Your statement is indeed what confuses most developers in their interpretation of what pseudo code is:
it does not describe the actual implementation. The latter is up to the developer to decide: its his job, his area of expertise. Pseudo code is just an (high level) algorithm with the basic sequence of steps taken to solve a problem.
True, most "pseudo code" is (wrongly) written to even at bit-level, using real named parameters and hence, an 1-to-1 translation (cut/paste) can easily be made. In fact most "pseudo code" is just actual code because they get the abstraction wrong.
Spoiler:
Pseudo code example
WHILE calibre files are present DO:
Input calibre file
IF calibre file genuine and valid DO:
clean calibre file TOC
store result
update bookkeeping
update database
update GUI where necessary
ELSE
inform user about failure
log failure
END
END
Print totals in GUI
But this is basic programming skill and actually IMHO
