Algorithms for Programmers|教育線上App不用買-HotApp4Game

Algorithms for Programmers - The printable full version will always stay online for free download. It is planned to also make parts of the TEXsources (plus the scripts used for automation) available. Right now a few files of the TEX sources and all extracted pseudo-code snippets1 are online. The C++-sources are online as part of FXT or hfloat (arithmetical Algorithms).

The quality and speed of development does depend on the feedback that I receive from you. Your criticism concerning language, style, correctness, omissions, technicalities and even the goals set here is very welcome. Thanks to those2 who helped to improve this document so far! Thanks also to the people who share their ideas (or source code) on the net. I try to give due references to original sources/authors wherever I can. However, I am in no way an expert for history of algorithms and I pretty sure will never be one. So if you feel that a reference is missing somewhere, let me know.

New chapters/sections appear as soon as they contain anything useful, sometimes just listings or remarks outlining what is to appear there. A ”TBD: something to be done” is a reminder to myself to fill in something that is missing or would be nice to have.

The style varies from chapter to chapter which I do not consider bad per se: while some topics (e.g. FFTs) need a clear and explicit introduction others (e.g. the bitwizardry chapter) seem to be best presented by basically showing the code with just a few comments. Still other parts (e.g. sorting) are presented elsewhere extremely well so I will introduce the basic ideas only very shortly and supply some (hopefully) useful code.

Sprache will partly go away: using/including the actual code from FXT will be beneficial to both this document and FXT itself. The goal is to automatically include the functions referenced. Clearly, this will drastically reduce the chance of errors in the shown code (and at the same time drastically reduce the workload for me). Initially I planned to write an interpreter for Sprache, it just never happened. At the same time FXT will be better documented which it really needs. As a consequence Sprache will only be used when there is a clear advantage to do so, mainly when the corresponding C++ does not appear to be self explanatory. Larger pieces of code will be presented in C++. A tiny starter about C++ (some good reasons in favor of C++ and some of the very basics of classes/overloading/templates) will be included. C programmers do not need to be shocked by the ‘++’: only an rather minimal set of the C++ features is used.

The theorem-like environment for the codes shall completely go away. It leads to duplication of statements, especially with non-pseudo code (running text, description in the environment and comments at the begin of the actual code).