Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index



Bjoern Michaelsen wrote:

Hi Norbert, all,

On Thu, 4 Aug 2011 20:47:43 -0500
Norbert Thiebaud <nthiebaud@gmail.com>
wrote:

The va_end manpage, on linux says:
"Each invocation of va_start() must be matched by a corresponding
invocation of va_end() in the _same function_"
 (emphasis is mine)
 so it's not just ugly, but also 'wrong'...

FWIW, I tried a clean new from the group up reimplementation of
SfxItemset once in cws new_itemsets:
...
Maybe somebody is interested in integrating the replacement Itemset? I
added an EasyHack for it:
 https://bugs.freedesktop.org/show_bug.cgi?id=39849
Although that is a truely challenging task, it would also be most
rewarding.

Best,

Bjoern


-- 
https://launchpad.net/~bjoern-michaelsen


_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

I don't know if i can do this easyhack but what about the 3 cases of vm_end
? Should vm_end be added ?
If yes, i can commit and pushed them for the 2 first cases. For the third
case, i can also do it but I can't check before since it impacts above all
Windows parts and I compile on Linux.

Julien.

--
View this message in context: 
http://nabble.documentfoundation.org/va-start-without-va-end-tp3223648p3235171.html
Sent from the Dev mailing list archive at Nabble.com.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.