Hi all,
I encountered bug #40459 [1] recently. It seems the bug has been ignored
because not many people encounter it and the original author did not
give feedback.
The issue is assigned to Wez. According to the git checkin history, he
doesn't seem to be a contributor anymore. I mailed him to see if he can
recommend someone to handle this issue, no response.
So my question is: can anyone familiar with the Stream Wrapper code take
a look at this issue? My C is not of sufficient level to fix this
myself. My idea would be to abstract creating a stream wrapper instance
and invoking the constructor to a separate function and calling that
function from the various functions that use stream wrappers, as the
amount of code needed to construct an instance and call the constructor
seems quite high to copy everywhere.
Kind regards,
Jorrit Schippers
Hi,
So my question is: can anyone familiar with the Stream Wrapper code take
a look at this issue? My C is not of sufficient level to fix this
myself. My idea would be to abstract creating a stream wrapper instance
and invoking the constructor to a separate function and calling that
function from the various functions that use stream wrappers, as the
amount of code needed to construct an instance and call the constructor
seems quite high to copy everywhere.
"Fixing" this is quite trivial.. except that it breaks any code
depending on the current behavior where people are using the constructor
in a way which might have an bad impact. This could only be done in
master.
Sometime ago I stumbled over that behavior it and had an additional
issue preventing me from fixing it, which I don't remember right now ...
johannes