On 09/10/12 23:47, Lucas De Marchi wrote: > classic. you can't take the address of a va_list, it will fail in very > different manners on different platforms/architectures. This means you > can't call va_arg() on different functions passing the arg around. > Unless you use some hacks. There's a hack that works pretty well. See > macro MAKE_PTR_FROM_VA_LIST() in edbus. > > A bit of info on the commit that introduced that macro: > http://git.profusion.mobi/cgit.cgi/lucas/edbus-history/commit/src/lib/edbus_private.h?id=16809d7cf38bf47b1dbef0e359695930a44c2752 >
Dear Lucas, yeah, we are aware that on different platforms it can be different things (e.g on raster's box it's a struct). If you are referring to the evas_box compilation errors, it can be solved in numerous ways. We just *always* pass pointers to it as it's more consistent and cleaner to handle. I don't understand what you wrote in the commit message there, as it does work correctly if you use pointers to the structures all the time (i.e va_list *). If you are talking about the segfaults: that's was just an oversight by myself that was fixed. I was inconsistent in some place in Eo that caused it not to work, doesn't seg anymore. -- Tom. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
