Quote:
Originally Posted by crutledge
Each modile should be accompanied by a pseudo code file defining and demonstrating the desired inputs, outputs, and data manipulation to be performed.
|
So you're saying write the code twice. Instead of reading pseudo code just read the code. All you're doing by writing pseudo code (other than writing the same thing twice) is writing code for someone who doesn't understand C++. If someone isn't versed in C++ it's still going to be difficult for them to contribute even if they know what the code is supposed to do. You still have to know C++ regardless.
Also, the user of pseudo code assumes you can represent the concept in the pseudo code. All you can do is show how something should work but not how it actually does work. For someone who knows C++ this is precisely what the class definition(s) in .h files do.
That said I will concede that Sigil could have more documentation. Especially when it comes to class dependance and how they work together.
Quote:
Originally Posted by crutledge
The US military tried to overcome these problems with ADA
|
And look how that turned out.