10/20/2023 0 Comments Pseudocode writerAbstract away from syntax and be easy to read. Which will have to be noted outside of the "pseudo-code." Moreover, books like "Introduction to Algorithms" like to use a mathematical syntax, which is violating one purpose of pseudo-code. Things like Q is nonsense when one needs to understand what Q is suppose to mean. "Introduction to Algorithms" book (by Cormen, Leiserson and Rivest) is a good book to read about algorithms, but the "pseudo-code" is terrible. This post is old, but hopefully this will help others. Note that Fortress is written in ASCII characters the special characters are rendered with a formatter. I must stress: this is not pseudocode, this is actual working Fortress code! From Also compare the implementation in a couple of other languages, like C or Fortran, and notice how they have absolutely nothing to do with the specification (and are also often an order of magnitude longer than the spec). For a fun experience, compare the specification of the benchmark with the implementation in Fortress and notice how there is almost a 1:1 correspondence. Here is an actual example of running Fortress code from the NAS (NASA Advanced Supercomputing) Conjugate Gradient Parallel Benchmark. ![]() ![]() You can leverage all that research by just looking at Fortress source code and abstracting out the things you don't need, since your target audience is human, whereas Fortress's is a compiler. In particular, for designing the syntax, they read and analyzed hundreds of CS and math papers, courses, books and journals to find common usage patterns for pseudocode and other computational/mathematical notations. This is an actual programming language, and not pseudocode, but it was designed to be as close to executable pseudocode as possible. I suggest you take a look at the Fortress Programming Language.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |