Re: [Gcl-devel] gcl sockets

[Camm Maguire]

Greetings!

Let me state first that I have yet to acquire much experience with
GCL's socket code, but I am interested in doing so and in ensuring
that the interface is robust and easy to use.  I do have experience in
this area in C.

In any case, a quick look through your example indicates that these
functions expect magic header bytes at the beginning of each exchange,
i.e. as when our-write is feeding data to our-read-with-offset.  The
relevant functions triggering your abort are in gcl-tk/comm.c

Needless to say, this should not be required.  There may be more
general interface functions elsewhere in the code -- I'll try to give
a more thorough look soon.  Suggestions/other experience most welcome.

Take care,

root <address@hidden> writes:

> Camm,
> 
> I'm having a bit of trouble with sockets in GCL.
> I can do:
> 
> (in-package "SYSTEM")
> (setq sock (open-named-socket 0))
> (setq conn (accept-socket-connection sock))
> (setq a 
>  (make-array 400 :element-type 'standard-char :fill-pointer 0 :static t))
> 
> but when I do:
> 
> (setq num (our-read-with-offset (caar conn) a 0 5 3000))
> 
> lisp waits for the read to complete and then exits.
> The function OUR-READ-WITH-OFFSET is given to lisp in o/new_init.c
> It references fSour_read_with_offset which seems to be undefined.
> 
> What am I doing wrong?
> 
> Tim
> 
> 
> _______________________________________________
> Gcl-devel mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gcl-devel
> 
> 
> 

-- 
Camm Maguire                                            address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah