Talk:Algorithms/Ada Implementation

A or B thats here the question.
Right now I want to start an Appendix for Ada implementations. I have allready got some text and working demos ready Ada Programming/Algorithms which I only have to move in here. Of course replacing the header and footer to fit the layout used here.

Since this page is only a "substub" and does not actualy have any real text in it (just instructions on what to put here) I consider replacing it (moving the instructions to the talk page) so the reader has some real text to read - Python programmers can allways start a new Appendix when they are ready and have some demos to put here.

Objections?


 * Go ahead. A for Ada sounds nicer anyway. When I suggested B I guess I figured there was more of a shell for the Python part. But since it's so empty, it makes more sense that A actually has something.

Guideline
implementations should be runnable (have a "main"), complete with some small test cases that demonstrate the use and correctness of the implementation, as well as show how it handles boundary cases. Output of the program should be included

Note 1
For all implementations, note when a library alternative exists. In these cases, show the correctness of the implementation by creating test cases that compare the results to the library answer.

Note 2
Note: The main text should includes links to these specific implementations.

TODO
Translate every program fragment in the text. There are sure to be bugs!