RE: IRC client
- Posted by bensler at mail.com Jan 14, 2002
- 426 views
I should mention, in case it misses you for some reason.. All the socket variables in all the routines need to be atoms.. I came across about 4 or 5 instances where it needed to be fixed.. I'm sure there are more. I never went thru the lib and fixed them all. I spose I should :P Chris Ray Smith wrote: > > bensler at mail.com wrote: > > Hi Chris (and Kat), > > I have taken your advice and attempted to update euTcp4u. > > I put the below changes into my source and tried to run my test > programs but they failed. > > With the changes you have made can you run the "server.exw" and > "client.exw" that come with euTcp4u? > > I left "connect_socket" as an atom but removed the second change and > my test programs work again. > Does your IRC code work if the second change is not used? > > I might also wrap the UDP functions as well ... see how I go. > > Regards, > > Ray Smith > > > > Ray, you really should post an update of eutcp4u, with the needed fixes, > > > > > > would save some trouble :) > > I haven't looked into it, but perhaps it's a similar problem with > > eulibnet, I wasn't able to connect with that one either. > > > > here is Kat's fix.. > > > > I found two bugs in tcp4u: > > > > line 505 in function tcp4u_connect() > > connect_socket should be an atom, it goes outside the range of integers > > > > lines: > > 495: port_addr = allocate(2) > > 496: poke(port_addr, port) > > > > make them into: > > > > port_addr = allocate(4) > > poke4(port_addr,port) > > > > That should be enough to get started. > > > Ray Smith > http;//www.geocities.com/ray_223 > >