From: Florian J. <fl...@wi...> - 2013-06-26 21:57:01
|
Hi is there any reason for Event wrapping around EventBase? There seems to be some refcounting mechanism, too, and complicated stuff Why don't we just specify a fully abstract class (Java programmers call it "interface"), and let WaveEvent and MidiEvent derive from this, and we're done? No EventBase pointers to be passed around or stuff. If there's no reason for this layer of indirection, i'd be glad to remove it. Greetings, flo |
From: Florian J. <fl...@wi...> - 2013-06-30 01:16:15
Attachments:
signature.asc
|
push If nobody calls "stop", I'll take your silence as a lack of reasons for this additional layer. Please tell me whether there is a reason, or tell me "no, go ahead". Thank you. Am 26.06.2013 23:56, schrieb Florian Jung: > Hi > > is there any reason for Event wrapping around EventBase? There seems to > be some refcounting mechanism, too, and complicated stuff > > Why don't we just specify a fully abstract class (Java programmers call > it "interface"), and let WaveEvent and MidiEvent derive from this, and > we're done? > No EventBase pointers to be passed around or stuff. > > If there's no reason for this layer of indirection, i'd be glad to > remove it. > > Greetings, > flo > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Robert J. <spa...@gm...> - 2013-07-01 17:34:54
|
Hey man, 2013/6/30 Florian Jung <fl...@wi...>: > push Just wanted to give a heads up that there is someone here.. > > If nobody calls "stop", I'll take your silence as a lack of reasons for > this additional layer. Sounds like a plan. Regards, Robert > > Please tell me whether there is a reason, or tell me "no, go ahead". > > Thank you. > > Am 26.06.2013 23:56, schrieb Florian Jung: >> Hi >> >> is there any reason for Event wrapping around EventBase? There seems to >> be some refcounting mechanism, too, and complicated stuff >> >> Why don't we just specify a fully abstract class (Java programmers call >> it "interface"), and let WaveEvent and MidiEvent derive from this, and >> we're done? >> No EventBase pointers to be passed around or stuff. >> >> If there's no reason for this layer of indirection, i'd be glad to >> remove it. >> >> Greetings, >> flo >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> Lmuse-developer mailing list >> Lmu...@li... >> https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |
From: Florian J. <fl...@wi...> - 2013-07-01 19:49:35
|
Am 01.07.2013 19:27, schrieb Robert Jonsson: > Hey man, > > 2013/6/30 Florian Jung <fl...@wi...>: >> push > > Just wanted to give a heads up that there is someone here.. Thank you, Robert :). Tim, what about you? > >> >> If nobody calls "stop", I'll take your silence as a lack of reasons for >> this additional layer. > > Sounds like a plan. > > Regards, > Robert > >> >> Please tell me whether there is a reason, or tell me "no, go ahead". >> >> Thank you. >> >> Am 26.06.2013 23:56, schrieb Florian Jung: >>> Hi >>> >>> is there any reason for Event wrapping around EventBase? There seems to >>> be some refcounting mechanism, too, and complicated stuff >>> >>> Why don't we just specify a fully abstract class (Java programmers call >>> it "interface"), and let WaveEvent and MidiEvent derive from this, and >>> we're done? >>> No EventBase pointers to be passed around or stuff. >>> >>> If there's no reason for this layer of indirection, i'd be glad to >>> remove it. >>> >>> Greetings, >>> flo >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Windows: >>> >>> Build for Windows Store. >>> >>> http://p.sf.net/sfu/windows-dev2dev >>> _______________________________________________ >>> Lmuse-developer mailing list >>> Lmu...@li... >>> https://lists.sourceforge.net/lists/listinfo/lmuse-developer >> >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> Lmuse-developer mailing list >> Lmu...@li... >> https://lists.sourceforge.net/lists/listinfo/lmuse-developer >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |