Hello Jan, you wrote: > > Since I am providing plugin versions of the most > > prominent SoX effects at > > https://github.com/prof-spock/SoX-Plugins > That begs the question: do you use libsox? That is to > say, do you call the functions of the undoccumented libsox > API? No, I reimplemented everything from scratch. The reason is that some SoX algorithms are distributed across the files, there is also some duplication and even different algorithm versions for similar tasks. And besides I wanted to use floating point arithmetic throughout. But others might need libsox: I do not. > > (reimplemented in C++, but functionally equivalent to > > SoX), > Eh, I'm not going there, sorry :-) Well, I think that C is still a good language for programming. But when you are using a C++-based framework for the plugin wrappers like JUCE, there is not much choice. And by the way: for complex projects I think that the abstraction mechanisms of C++ are really helpful. > > But I have one suggestion for your repository: I would > > appreciate it when all the SoX sources are in some > > subdirectory like e.g. src. If you left all sources as > > is, this would clutter up the top level and obscure > > things like the readme or the build shell files. > Why? > Obscure in what sense? > Not standing out in a ls(1) of the directory? The top level directory currently contains source files, build files, the readme, license etc. Hence the many source files "obscure" other files. "Clutter up" would also be a good description. > That is a tiny price to pay, compared to the needless > complexity of having subdirs and havein make(1) run > recursively. I am not at all advocating recursive makefiles. You can have a single make file (top-level ;-) which references files in subdirectories. The SoXPlugins project mentioned above uses a single CMake file doing exactly that (which - by the way - is itself contained in a subdirectory buildSetup together with some include files needed). But this is only my suggestion: you are the maintainer now and can do what you deem appropriate. Best regards, Thomas _______________________________________________ Sox-users mailing list Sox-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/sox-users
