[SoX-devel] Keeping skeletons in the closet

[Reuben T. <rr...@sc...>]

I have been thinking about the skeleton code (you may have noticed various 
checkins to the two files) and the more I think about it the more I think it 
would be better to keep the two files, but compile them in and add tests for 
them.

The reason is that any effect or format has non-typical features which 
distracts from the "model" nature of the skeletons. I am in the process of 
adding a Lua file format (i.e. the ability to write file formats in Lua), 
and I thought I could use the Lua effect and format as the skeletons, 
because basically they do nothing (the actions in each case consisting of 
handing off to Lua scripts), but in fact even they have individualities (in 
particular the way that Lua effects currently have a do-nothing flow stage).

So, unless you're agin', I propose compiling in and documenting the skeleton 
effect and format, and adding tests. This will make them more useful (they 
might be helpful for debugging and will certainly be closer to bug-free) and 
ensure that they are kept up-to-date (hopefully with little effort).

-- 
http://rrt.sc3d.org/ | The shorter the better