On Sun, 2007-04-22 at 17:47 +0200, Miguel Lobo wrote:
>
> Definitely. As I mentioned, that name was just meant as a joke and I
> hope nobody took it in any other way. In fact, I have already renamed
> the fork to something else completely Fluidsynth-unrelated.
>
Ok, I hadn't realized that na
On Sun, 2007-04-22 at 17:16 +0200, Miguel Lobo wrote:
>
> Sure. I just mean that talk is cheap. Technical flamewars on OSS
> mailing lists tend to involve many people with strong opinions, even
> people whose contribution to the project in question in terms of code
> are slim to none. That doe
> Anyway, I believe in the usefulness of the "show me the code"
> approach in these situations. Many people have strong opinions on
> some technical issues, but not so many are usually willing to
> translate those opinions into actual working code.
Hmm, interesting opinion. Could you be more sp
On Sat, 2007-04-21 at 21:13 +0200, Miguel Lobo wrote:
> Oh, my understanding from yesterday's discussion was that the decision
> had indeed been made. The belief in maintaining the statu quo seemed
> fairly strong around the list.
It didn't really seem like a decision was made to me, it was jus
It didn't really seem like a decision was made to me, it was just that
the overall consensus seemed to indicate that continuing to support
existing FluidSynth users is important. It sounds to me like you would
like to have your own FluidSynth based project which is coded in the way
that you woul
On Apr 21, 2007, at 9:13 PM, Miguel Lobo wrote:
Anyway, I believe in the usefulness of the "show me the code"
approach in these situations. Many people have strong opinions on
some technical issues, but not so many are usually willing to
translate those opinions into actual working code.
Hello Marcus,
Those functions aren't in the public headers. I can see how they might
be useful to external programs, but they should be considered private
currently. They do seem to be mostly macros though, so I imagine you
could probably get away with just including the header in your code, but
