I fail at python sockets, hard

I'm trying to make something that once it is disconnected will automatically try to reconnect.  I'll add some more features in later so it doesn't hammer the server but right now I just want to keep it simple and get that part working.  The problem is that when I use sock.close I get an error message of
Bad File Descriptor
and if I either use shutdown or just go straight to reconnecting I get:
Transport endpoint is already connected

This is what I've got right now:

#! /usr/bin/env python
import socket, string
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
def doconn():
    sock.connect(("localhost", 1234))
def dodiscon():
    sock.close()
    doconn()

doconn()

while (1):
    buffer = sock.recv(1024)
    if not buffer:
        dodiscon()


What am I doing wrong?

Read SICP

[code] tags are there for a reason, for fuck's sake.

>>3
EXPERT BBCODE PROGRAMMER

>>3
one word, THE FORCED INDENTATION OF CODE, thread over.

strange

you clearly don't understand what the connect() actually does. Do some reading and try again. (Pro-tip: it's a shortcut to bind on a non-specified port)

>>5
FIOC won't help if you use a proportional font.

Just recreate the socket

Create a new socket for each connection instead of calling connect() again on the old one.
And while (1): ? Those parentheses are superfluous and misleading.
And dodiscon is convoluted, and inconsistent with doconn (note the n's). Put in the extra typing effort and give them full names, like do_disconnect. But it's not really a disconnect, it's a reconnect, so change the name to reflect that.

#! /usr/bin/env python
import socket, string
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
def doconn():
    sock.connect(("localhost", 1234))
def dodiscon():
    sock.close()
    doconn()

doconn()

while (1):
    buffer = sock.recv(1024)
    if not buffer:
        dodiscon()

Sockets in general are just fucking retarded and impossible.

I really don't think I want to be a programmer anymore.

Good choice

While we're on the topic of sockets, I have a question for [spoiler]/prog/[spoiler]:

Say your UNIX application connects to some server, and is doing normal read and write stuff, and then suddenly the socket dies. What do you do? Do you try to reconnect, or do you abort the whole program with an error? Maybe you do some hybrid approach that tries to reconnect a couple times at increasing intervals of time, and then abort after a while.

Well [spoiler]/prog/[spoiler], tell me.

>>14
It depends on what the program is doing.

>>15
Wrong answer.

>>14
Totally DDOS the host with the string "DON'T FUCK WITH MY SOCKET\0"

>>17
That's not a string, it's an array of bytes.

>>16
Wrong reply.

Another question for the programmers of /prog/:

Say you have a data structure in C, and you have a function to malloc a new structure, and return it et cetera.

Do you create a function and get passed in a pointer to a pointer to a struct, or return a pointer to a struct:


int
ds_init(struct ds **ptr)
{
  *ptr = malloc(sizeof(**ptr));

  // Of course you can return more interesting integers for errors et cetera.
  return 1;
}

>>20
I use macros and call abort() if malloc fails, of course!

>>21
EXPERT PROGRAMMERs use exit()!

>>22
Did you mean ExitProcess(NULL, NULL, NULL, NULL, NULL)?

>>23
I'm sorry, I use Ubanto, the one true operating system!

I crossposted this to 10 different forums and eventually got an answer on IRC.  Close doesn't just disconnect the socket, it completely fucking wipes it from the face of the planet.  So I just had to create a new one with the same name and it was fixed.

>>25
Try reading the documentation next time.

the problem is not close(). The problem is that you don't understand what connect() does

>>25
Congrats, you're a retard.

Return function 75 var 76 if 73?