Do you have an example or can you explain how to find these. I'll have a
look.
On 02.03.19 04:31, Patricia Shanahan wrote:
> The OpenOffice build system is both complicated and fragile. If you do
> move things around, you MUST test the ability to build and install for
> each supported OS.
>
> To m
One starting point is my last few patches, which involved a bug in one
of the string implementations, and buffer overflows.
On 3/1/2019 11:58 PM, Peter Kovacs wrote:
Do you have an example or can you explain how to find these. I'll have a
look.
On 02.03.19 04:31, Patricia Shanahan wrote:
The
FWIW, I agree. We've already seen how simple, obvious changes have a nasty
ripple effect. Having a major restructure "now" would, from what I can see,
have a major impact on us being able to release 4.2.0 in anything close to
"soon"...
I also have issues w/ fixing/restructuring things that work
My motivation for wanting to update data structures is bug fixing. I've
already had to track down and fix buffer overflows. A general move to
self-expanding buffers and bounds checking would fix bugs we do not yet
know about.
On 3/2/2019 7:16 AM, Jim Jagielski wrote:
FWIW, I agree. We've alre
Error 1305. Can you help?
Sent from Mail for Windows 10
