Re: NSSound Reimplementation

2009-06-19 Thread Fred Kiefer
Stefan Bidigaray wrote: > It would really help if I attached the file... > I don't understand the general concept here, so just a few detail comments on the code itself. Hiding the implementation details in the header is a good thing, but it makes the code in the implementation harder to read. T

Re: NSSound Reimplementation

2009-06-19 Thread Richard Frith-Macdonald
On 19 Jun 2009, at 08:05, Fred Kiefer wrote: Stefan Bidigaray wrote: It would really help if I attached the file... I don't understand the general concept here, so just a few detail comments on the code itself. Hiding the implementation details in the header is a good thing, but it make

Re: NSSound Reimplementation

2009-06-19 Thread Stefan Bidigaray
On Fri, Jun 19, 2009 at 2:05 AM, Fred Kiefer wrote: > I don't understand the general concept here, so just a few detail > comments on the code itself. > I'll try to explain this the best I can, it might be a little long, though... As I explained on my previous e-mails, I'm streaming the data to

Re: NSSound Reimplementation

2009-06-19 Thread Stefan Bidigaray
On Fri, Jun 19, 2009 at 4:26 AM, Richard Frith-Macdonald < rich...@tiptree.demon.co.uk> wrote: > I would go further and ask what the point of the _private array is? Well, the only reason I could come up with right now is that I didn't want to have to include GSSoundSink.h and GSSoundSource.h. T

Re: NSSound Reimplementation

2009-06-19 Thread David Chisnall
On 19 Jun 2009, at 17:30, Stefan Bidigaray wrote: Then the designated initialiser allocates memory for the structure, clears it, and assigns the pointer when an instance is initialised, and -dealloc frees the memory at the end, and all internal references to ivars just go indirect from that