Hi Istvan, Just wanted to say that I appreciate your work very much and your willingness to work out issues on some of the requests I've had the past couple of months(and really the past years of all your work!). They've been really quite invaluable and have helped make my Csound work a lot easier and enabled many new techniques. I hope you have not felt unappreciated for all of your hard work over the years, as I am more than certain that the contributions and direction you've been setting have been on the whole very appreciated. That said, I recognize that contributing to Csound--be it code, documentation, or simply new ideas--is a lot of work and a lot of free time, something which takes away from our own music making time and simply anything else we enjoy doing with our time. Please don't feel obligated in any way to contribute in the future, after all your time is your time, but do know that your contributions both in code and on this mailing list are appreciated. And if you should find yourself wanting to contribute your time in the future on the code base, then all the better for everyone I think (and that of course goes for everyone contributing, as everyone brings new ideas and helps push the program forward!). So, thanks again for all your work and best of luck in your other endeavors! steven On 10/18/05, Istvan Varga wrote: > I changed csound.lisp in an attempt to update it for changes made to > some API functions, but it appears that I should not have tampered > with it. > Your new API functions are redundant, do not add new functionality, > are very limited (do not allow for additional arguments or even compiling > an orc/sco pair instead of a csd), and are not useful for anything other > than saving two lines of code in a host application. I think the API is > better kept clean and minimal without spamming it with redundant functions. > You also broke the binary layout of the CSOUND structure. > I do not really care, though, as I decided not to commit any more code > to the csound5 CVS module for one year or when Csound5 is released, > whichever is later. If people think that I became an old relic that > only holds back the work of others, now there is a chance to do everything > on your own, I will not interfere. Feel free to add anything, rewrite > Csound in C++, integrate wrappers, or whatever you want. > I will still update the manual, and answer questions not related to > development on the lists, but it is time to take another long break > so that I have time to other things. > > Michael Gogins wrote: > > > I note that Istvan Varga took it upon himself, without discussion or > > consultation, to remove some functions that I recently contributed to > > the Csound API. > > > > He also edited the csound.lisp file so that it is no longer usable, > > leaving me to fix up his mistakes. > > > > I have, of course, immediately restored the code and I will restore it > > again if I have to, though I am willing to discuss what I am doing, as I > > have been discussing it all along. > > > > It is not proper for one developer, no matter how talented they are or > > how useful their work has proven -- and I freely acknowledge Istvan's > > worth on both counts -- on an open source project such as Csound to > > unilaterally remove or greatly modify the work of other developers. > > > > It also is not proper to work on code without testing it. > > > > The purpose of the work I am now doing, as I have discussed previously > > here, is to expose the Csound API to LISP. I will extend this to expose > > the API to Python, Java, and possibly Lua as well. This code may be > > built into the Csound shared library, or it may be built as a separate > > shared library, as we decide. > > > > As part of this work, I have found that calling functions of the form > > (int, char**) for example in csoundCompile(int argc, char** argv) is not > > always the most convenient from the standpoint of the user of the API > > and not always the easiest to call from a foreign function. Therefore, I > > added > > > > int csoundCompileCsd(CSOUND* csound, char *filename) > > int csoundPerformCsd(CSOUND * csound, char *filename) > > > > With these changes the Csound API is now easily usable directly from > > CLISP, and this binding should work on all CLISP-supported platforms > > including Linux, WIndows, and the Macintosh. Once this is working, I > > plan to change it from CLISP FFI to CFFI or UFFI, which should be usable > > with other implementations of LISP as well. > > > > I also have contributed a set of functions to enable users of the API to > > programmatically build up a CSD file in memory, and especially, to > > append 'i' events to the Csound score a line at a time, either as > > strings, or as floating-point pfields. > > > > The purpose of these functions is so that the composer can 'embed' the > > Csound instruments and command-line options directly in the LISP, > > Python, or whatever file that constitutes a pieces. In my experience, > > this makes it harder to lose pieces of what one is working on, and > > speeds up the working process. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net