> On March 27, 2016, 10:03 a.m., David Faure wrote:
> > Given how the socket API works, you should only call error() after a call
> > that returns false (e.g. waitForConnected, etc.). As you found out, calling
> > error() at random points in time doesn't give useful information, you get
> >
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/127501/
---
(Updated March 31, 2016, 8:01 p.m.)
Status
--
This change has been
> On March 27, 2016, 10:03 a.m., David Faure wrote:
> > Given how the socket API works, you should only call error() after a call
> > that returns false (e.g. waitForConnected, etc.). As you found out, calling
> > error() at random points in time doesn't give useful information, you get
> >
> On March 27, 2016, 10:03 a.m., David Faure wrote:
> > Given how the socket API works, you should only call error() after a call
> > that returns false (e.g. waitForConnected, etc.). As you found out, calling
> > error() at random points in time doesn't give useful information, you get
> >
> On March 27, 2016, 10:03 a.m., David Faure wrote:
> > Given how the socket API works, you should only call error() after a call
> > that returns false (e.g. waitForConnected, etc.). As you found out, calling
> > error() at random points in time doesn't give useful information, you get
> >
> On March 27, 2016, 10:03 a.m., David Faure wrote:
> > Given how the socket API works, you should only call error() after a call
> > that returns false (e.g. waitForConnected, etc.). As you found out, calling
> > error() at random points in time doesn't give useful information, you get
> >
> On March 27, 2016, 10:03 a.m., David Faure wrote:
> > Given how the socket API works, you should only call error() after a call
> > that returns false (e.g. waitForConnected, etc.). As you found out, calling
> > error() at random points in time doesn't give useful information, you get
> >
> On March 27, 2016, 10:03 a.m., David Faure wrote:
> > Given how the socket API works, you should only call error() after a call
> > that returns false (e.g. waitForConnected, etc.). As you found out, calling
> > error() at random points in time doesn't give useful information, you get
> >
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/127501/#review94042
---
Given how the socket API works, you should only call error()
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/127501/#review94033
---
Ow. That's a pretty bad problem.
I suggest a less intrusive
10 matches
Mail list logo