> I think a core commenting sprint would be *very* helpful, specially to those > of us > (me) who would like help in understanding the black magic inside. Does anyone know a tool that will display the line number of a vim session in a large rectangle next to the terminal window? The one could do a screencast and just scroll down through the source explaining what each block of code does. Then people could just search youtube for the relevant c source file, and queue up the video and search until the relevant line number appears in the big rectangle.
-Jonathan -------- Dan Wilcox @danomatika danomatika.com robotcowboy.com On Oct 19, 2016, at 12:57 PM, [email protected] wrote: That is an important question. Pd code is full of clever tricks and bit hacks for dsp efficiency. What is the origin of q8_rsqrt(), why and how does it work? What about PD_BIGORSMALL() in m_pd.h? And the mysterious UNITBIT32 number in d_osc.c? Ideally such code should be commented not only to denote its function (if necessary) but also to reference the origin so you may be able to find info. _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
