Is there necessary to write the ngspice development document?
If it is , and if I want to(I dont know whether I have the ability and whether be welcomed), where should I begin to ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What is your definition of "the ngspice development document"?
A great help would be if you could systematically test parts (or all) of the code base against the ngspice manual. For example, you could put together a re-usable test suite that tests all possible .MEASURE and MEASURE statements, or all possible features of PLOT, or all possible numerical boundary cases of the build-in functions (like sinh).
Such tests only work if the manual is complete (it isn't). You could also go from the sources upwards and test that they do what they say. The problem is that the comments are scarse, but the code iself can't lie. This eventually would improve the manual.
-marcel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there necessary to write the ngspice development document?
If it is , and if I want to(I dont know whether I have the ability and whether be welcomed), where should I begin to ?
What is your definition of "the ngspice development document"?
A great help would be if you could systematically test parts (or all) of the code base against the ngspice manual. For example, you could put together a re-usable test suite that tests all possible .MEASURE and MEASURE statements, or all possible features of PLOT, or all possible numerical boundary cases of the build-in functions (like sinh).
Such tests only work if the manual is complete (it isn't). You could also go from the sources upwards and test that they do what they say. The problem is that the comments are scarse, but the code iself can't lie. This eventually would improve the manual.
-marcel
why not