> Le 29 nov. 2017 à 10:04, Hermann Meyer <brumm...@web.de> a écrit : > > > > Am 29.11.2017 um 09:27 schrieb Stéphane Letz: >> Thanks Hermann. >> >> Although we know the work done for the guitar project, we do not (in >> general…) recommend hacking the generated C++ code. The reason is that since >> the compiler class output shape may change.., this method can be quite « >> fragile ». > > Hi Stéphane > > Yes, I know how fragile it could be, as we use this method now several years. > In this time we need to upgrade our script several times to follow the faust > development. > I've just ported guitarix from faust 0.9.73 to the latest faust 0.9.90 which > requires 2 days.
Yes the summer 2016 library change was a *big* change (thanks again to Romain for this…) We hope that the new structure is much more stable now... > But most time I spend on the faust sources to port them to the new library > architecture. > The transforming of our dsp2cc script was just a few lines to cover the > compiler output. > As next I'll check out how it works with faust2. BTW, how does the dsp2cc script works if you generates the vector kind of C++ code, that is using -vec -lv xx kind of parameters in the faust command line ? > > Surely it could be possible to subclass it, just we are used to use our > parser and in the meantime this structure is deep bounded into our sources. > > regards > hermann Yep, my point is to warn developers, then everyone can do whatever they want, to fit their needs... ((-; Stéphane ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Faudiostream-devel mailing list Faudiostream-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
