If it's the default yes, because I did not change
my build options (packages are ready). I think that
that we are probably safe as the PV bus has not (to
my knowledge) been widely used. However, if the
new members had been added to the end of PVSDAT and
PVSDATEXT, perhaps we would have been safer (?).

IMHO, we can go ahead with these changes without
much ado.

Victor

> So, are the rest of you using SDFT for building the
> releases?
>
> Do the changes to PVSDATEXT constitute an incompatible
> change in the API?
>
> Anthony
>
> Victor Lazzarini wrote on 10/2/07 5:42 AM:
>
> > PVSDATEXT should match PVSDAT apart from the AUXCH data
> > member, which is a float *. Otherwise, pvsbus will not
> > work. I have added the changes to it.
>
>
> ----------------------------------------------------------
> --------------- This SF.net email is sponsored by:
> Microsoft Defy all challenges. Microsoft(R) Visual Studio
> 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net