🚀 go-pugleaf

I have an application which uses Unix-style socket calls, to which I'm
attempting to add SOCKS support.

Indy supposedly supports SOCKS, so I'm trying to figure out how to
convert the normal socket code to the bizarre usage of Indy.

I'm using BCB6 for the app in question, so I removed Indy 8,
downloaded the latest Indy10 snapshot, and installed that (apparently
successfully).

Since the high-level protocol in use is proprietary, I'm using
TIdTCPClient.  I'm assigning a TIdIOHandlerStack to the IOHandler
property, and a TIdSocksInfo to the TransparentProxy property of the
IOHandler (though I've also tested with no proxy set - results are the
same).

One problem is that there's no simple functional equivalent of recv()
for the IOHandler.

I've tried ReadBytes() and ReadLn(), preceded by Readable() to make
sure the socket can be read (that functionality is a must), just to
get started on simply reading any data from the socket.

I connect to a server I control, which sends data over the socket as
soon as it's connected.  I've confirmed with packet capture that the
correct data is sent.

However, while Readable() returns true, both ReadBytes() and ReadLn()
read nothing at all.  The Length property of the TDynByteArray sent to
the former is 0, and the return string for the latter is empty.  Yet
calling them made the result of Readable() subsequently false.

What is the correct way to simply read and write a socket?