> On Mar 21, 2015, at 1:48 PM, Hazen Babcock wrote:
>
> On 03/20/2015 05:35 PM, Jim Dishaw wrote:
>>>
>>> In sum, the technical choice is between the alt approach which
>>> requires already implemented code in the core with simpler code in the
>>> unicode-aware drivers and the original approach
Alan,
Thanks for the update. I'm glad you managed to track it down. I'd held of
delving into this as you seemed to have it under control. I'm also
slightly surprised at the linker not being more intelligent here.
Certainly something we need to be wary of.
Andrew
On Sat, Mar 21, 2015 at 11:57:20
Just to summarize where we stand there are several open-ended issues
blocking the release.
1. I am in the middle of a hunt for plend memory management issues caused by
redundant
library linking (see previous post to Andrew).
2. Because of issues like the qt_example segfault that I have just
fixe
Hi Andrew:
I have now (commit fa0c879) solved this release-critical regression.
The crux of the problem is redundant linking of qt_example to both
plplot (which contained all of the code in plplotqt for this
ENABLE_DYNDRIVERS=NO case) and plplotqt. examples/c++/qt_example had no severe
memory man
On 03/20/2015 05:35 PM, Jim Dishaw wrote:
>>
>> In sum, the technical choice is between the alt approach which
>> requires already implemented code in the core with simpler code in the
>> unicode-aware drivers and the original approach which allows us to
>> drop core code at the expense of more dup
On 2015-03-20 08:46-0400 Hazen Babcock wrote:
>
> Hello,
>
> Since we are considering a number of changes, such as fixing error
> handling, that would break backwards compatibility anyway I propose that
> we think a bit about all the other things that we might like to change,
> perhaps bringing us
