Documenting FFTS

[robertmassaioli]

Using knowledge of how the DFT is supposed to work (by reading through the DSP Guide) and by reading through the source code, I was able to work out how this library is supposed to be used. However, the code can do with some documentation. I have the following questions:

• I was wondering roughly how long until you intended to update the "Coming Soon" on the Documentation Page?
• In bullet point form, what content did you want to appear / were you planning to write on the blank Documentation page?
• If you had no plans to write up that guide then please let me know, I was planning to write a blog post about it and you can take anything from that blog post that you like. (This is just a heads up)
• Instead of "Coming Soon", why not link back to this issue on the documentation page.

At any rate, thankyou for writing FFTS, it is awesome and permissive. You rock.

[madscientist159]

I'd also like to see some basic documentation (with C equivalants or even pseudocode) on the assembler portions of ffts and how they interact with the code generator. Right now ffts is locked to only a handful of architectures and I don't know where to start if I were to port it to a new architecture.