Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 04/29/24 in all areas

  1. Sherlock

    A gem from the past (Goto)

    That reminds me:
  2. Remy Lebeau

    TCP Port Check with timeout

    You are leaking the socket handle if connect() fails. You have to close the handle if socket() succeeds, regardless of whether connect() succeeds. You can't reduce (or even set) the timeout on a blocking connect(). You have to use a non-blocking connect() and then use select() or equivalent to implement the timeout. AFAIK, you can't disable SACK on a per-socket basis. You have to use the Registry or command-line netsh utility to disable it globally: https://superuser.com/questions/1808254/how-to-disable-tcp-sack-in-windows-xp https://www.linkedin.com/advice/3/how-can-tcp-selective-acknowledgment-sack-improve-heatc
  3. Bill Meyer

    A gem from the past (Goto)

    There is a classic, if dusty, article from Donald Knuth: https://pic.plover.com/knuth-GOTO.pdf
  4. dummzeuch

    Delphi and "Use only memory safe languages"

    Since Delphi is kind of a legacy programming language nowadays, backwards compatibility is very important. You don't want to throw away millions lines of proven code because they don't work any more, or even worse, because they are now buggy. So trying to change strings to be zero based was a bad idea, even if it was "just for mobile platforms".
×