Bug#871649: lv2-dev: abuse of non portable pointer of uint8_t type

Hi Code like this might destabilize the operating system and compromise debian. There is a good reason why glib-2.0 uses void pointers. Bests, Joël On Fri, Aug 11, 2017 at 9:23 PM, Joël Krähemann wrote: > Hi > > Might be just a programming error. But it is important

Bug#871649: lv2-dev: abuse of non portable pointer of uint8_t type

Hi Might be just a programming error. But it is important that you don't point uint8_t pointer to a struct. Might be some language basics missing? It is the same for atoms. Just use void pointers, please. Bests, Joël On Fri, Aug 11, 2017 at 8:52 PM, Robin Gareus wrote: >

Bug#871649: lv2-dev: abuse of non portable pointer of uint8_t type

Note that the LV2 event extension was deprecated years ago and the last plugins which were using it were /killed/ in 2014. http://lists.lv2plug.in/pipermail/devel-lv2plug.in/2014-January/000642.html As for the bug report itself, changing plugin API specifications post-factum is never a good

Bug#871649: lv2-dev: abuse of non portable pointer of uint8_t type

Hi For sure you can cast any pointer. But feels somehow wrong. The opinion was the specs are always correct. Bests, Joël On Fri, Aug 11, 2017 at 8:12 PM, Jaromír Mikeš wrote: > > > 2017-08-10 16:23 GMT+02:00 Joël Krähemann : >> >> Hi James, >> >>

Bug#871649: lv2-dev: abuse of non portable pointer of uint8_t type

Hi James, It is common that you use for storing uint8_t an entire word. The use of a uint8_t pointer confused me as you are pointing to a struct. Bests, Joël On Thu, Aug 10, 2017 at 4:10 PM, James Cowgill wrote: > Hi, > > On 10/08/17 08:31, Joël Krähemann wrote: >>