Interesting trees week 31

2009-07-27 Thread Anders Waldenborg
Merged: * Lots of minor cleanups from caotic/master * Ruby 1.9.1 fix from tilman/master * _GNU_SOURCE removal from puzzles/master * xmmsclient++ wscript fix from anders/master New stuff: * tilman/genipc has 29 changes not in devel. All are real! Now generates some serverside code. Cool.

Re: Interesting trees week 31

2009-07-27 Thread Tilman Sauerbeck
Anders Waldenborg [2009-07-27 18:53]: > New stuff: > * tilman/genipc has 29 changes not in devel. All are real! > Now generates some serverside code. Cool. Yes, it even seems to work. Just pushed a crappy hack that makes things build, too. > Any ideas on how to do signals/broadcasts?

Re: Interesting trees week 31

2009-07-27 Thread Anders Waldenborg
Tilman Sauerbeck wrote: Any ideas on how to do signals/broadcasts? Not yet, that one's next. I had some idea that each ipc exported object created a struct like this: typedef struct { void (*meth_start) (xmms_output_t *, xmms_error_t *); void (*meth_stop) (xmms_output_t *, xmm

Re: Interesting trees week 31

2009-07-28 Thread Tilman Sauerbeck
Anders Waldenborg [2009-07-27 21:52]: > Tilman Sauerbeck wrote: > >> Any ideas on how to do signals/broadcasts? > > > >Not yet, that one's next. > > I had some idea that each ipc exported object created a struct like this: > > typedef struct { > void (*meth_start) (xmms_output_t *, xmms_

Re: Interesting trees week 31

2009-08-01 Thread Tilman Sauerbeck
Tilman Sauerbeck [2009-07-28 19:07]: > Anders Waldenborg [2009-07-27 21:52]: > > Tilman Sauerbeck wrote: > > >> Any ideas on how to do signals/broadcasts? > > > > > >Not yet, that one's next. > > > > I had some idea that each ipc exported object created a struct like this: > > > > typedef str