Upstream API breakage question

2008-02-19 Thread William Pitcock
Hi, libprojectM upstream are soon releasing libprojectM 1.1 which makes the following breakage: public: PCM *projectM::pcm is replaced by: public: const inline PCM *projectM::pcm() { return _pcm; } So, is this the proper solution: * libprojectm1 - libprojectm2 * libprojectm-dev -

Re: Upstream API breakage question

2008-02-19 Thread Michal Čihař
Hi On Tue, 19 Feb 2008 03:43:09 -0600 William Pitcock [EMAIL PROTECTED] wrote: libprojectM upstream are soon releasing libprojectM 1.1 which makes the following breakage: public: PCM *projectM::pcm is replaced by: public: const inline PCM *projectM::pcm() { return _pcm; } So, is

Re: Upstream API breakage question

2008-02-19 Thread Hamish Moffatt
On Tue, Feb 19, 2008 at 03:43:09AM -0600, William Pitcock wrote: libprojectM upstream are soon releasing libprojectM 1.1 which makes the following breakage: public: PCM *projectM::pcm is replaced by: public: const inline PCM *projectM::pcm() { return _pcm; } So, is this the proper

Re: Upstream API breakage question

2008-02-19 Thread Bernhard R. Link
* William Pitcock [EMAIL PROTECTED] [080219 10:40]: libprojectM upstream are soon releasing libprojectM 1.1 which makes the following breakage: public: PCM *projectM::pcm is replaced by: public: const inline PCM *projectM::pcm() { return _pcm; } So, is this the proper solution: What