[Qt-interest] Why Bus error clientSocket->waitForConnected()?

[Kustaa Nyholm]

> the only issue is

That is definitely not the ONLY issue

> that Java developers, may find the difference in readLine()

but indeed it is an issue when a library takes a deviating
route for no apparent reason, for seemingly no purpose,

> subtle and confusing.

the subtleness is indeed the problem, why name something
in a way that suggests something but behaves subtly but
drastically differently?


>Experience QT developers (or those who never used Java's  readLine()) won't
>have any problem.

For any API feature you can say the same.


Apparently no-one is interested in discussing if there is any
reason for the readLine() design, why it is the way it is?

Is there any use case for it? Any use case where the simpler
Java readLine / C std lib getline design could not be used?

Everyone so far seems to be on the defense, but I'm interested
if there really is a reason for this decision or if it was just
a mistake. I respect the designers of Qt so I suspect there was
a reason, valid or not, and would like to understand it.

br Kusti