Will,
On Sat, 2010-10-23 at 15:41 -0400, William Lachance wrote:
> I imagine I could convert everything libwpd-related (libwpd,
> writerperfect, bindings, libwpg, the abiword plugin) to this approach
> (with the insertSpace function I mentioned above) in the space of an
> afternoon next week.
Ok,
2010/10/23 Fridrich Strba :
> Will,
>
> My first wild idea is that if you do it all properly, go for it. Like to
> be sure that we don't require user to free anything she did not allocate
> and that we don't return reference to a temporary from a function, try
> it.
const char * implies read-only,
Will,
My first wild idea is that if you do it all properly, go for it. Like to
be sure that we don't require user to free anything she did not allocate
and that we don't return reference to a temporary from a function, try
it.
Now, concerning the binding, we don't have big issues with binding
lib
On Sat, 2010-10-23 at 11:45 -0400, William Lachance wrote:
> Hey,
>
> So after having come back to libwpd after a few years, I realized that
> I made one mistake when designing the external API.
>
> For various reasons (OOo compatibility, language bindings) we don't
> want to export STL structure
Hey,
So after having come back to libwpd after a few years, I realized that
I made one mistake when designing the external API.
For various reasons (OOo compatibility, language bindings) we don't
want to export STL structures (string, map, etc.) in the external API.
For this reason, I created a c
