Re: TCP/IP Sockets with GNAT.Sockets

fabio de francesco wrote:
From my message: "...I am relying on comments in file g-socket.ads from 
GCC/GNAT sources...". Sorry for my poor English, I know that sometimes
I'm unable to express clearly, but I had already done exactly what you
now suggest.
[...]
I also said I already know how to program with sockets in C.

i'm sorry if you misunderstood my words: i just wanted to make clear that you did exactly what you had to do, and that there was no other way to go.

the only big difference is in Streams, which is Ada specific...

(this was just an introduction for the next big paragraph...)(french style)

[...]
Thank you for this detailed explanation. 

you're welcome !

This is exactly the problem that I have overcome with the help I've had
from Eric Jacoboni. Both my client and server programs didn't work at
exchanging messages with C programs. After searching the web I
discovered I had to use Receive_Socket() and Send_Socket() in order to
get over that problem.


that's plain wrong...

the problem is the use of attributes 'Output on arrays which output array bounds before array data. and since String is an array, String'Output outputs String bounds before string data. (in Ada you are no more in C: a string is not delimited by a null character but has a lower and an upper bound).

those bounds are always getting in the way when:
1. you are not aware of their existence on the stream
2. the reader of the stream is not an ada program.

anyway, you can get rid of those bounds by using 'Read and 'Write instead of 'Input and 'Output. BUT you have to know that using 'Read on unconstrained arrays (especially on String) is... well... A Bad Thing(tm). (i'm not even sure it works).

you should note that the problem is the same in C: when reading a string (sorry an array of char) from a socket, you don't know its length. how can you say you read the whole string, and not a sub-part, or worst, the whole string plus the beginning of the following data ?

if you can overcome this problem in C, rest assured you can overcome it in Ada...
(the exact default behavior for stream attributes is detailed in ARM95 13.13.2: this includes the behavior for array bounds, type discriminants, tags...)

S : String := "Hello";
SEA : Stream_Element_Array(1..S'Length);
for SEA'Address use S(S'First)'Address;
Last : Stream_Element_Offset;
Send_Socket( Socket, SEA, Last );


(i'm sorry i'm gonna be a bit rude) beuark !

this is implementation dependant:
- what if Character'Size /= Stream_Element'Size ?
- what if the memory organization of Stream_Element_Array does not match the one for a String ?
(i'm not sure overlays are not a recommended practice, but i may be wrong)

you'd better write this:

declare
    Socket : Socket_Type;
    Channel : Stream_Access;
begin
    -- open your socket here, then...
    Channel := Stream( Socket );

    String'Write( Channel, "Hello" );
    -- close your socket here...
end;


This is not exactly what someone can find in a Python or C manual. :-) 

i won't put it in an Ada manual either !!

You're right about the fact that the fault is mine for not knowing
Streams while a Socket package isn't required to give any explanations
on the usage of a subject that is not so closely related.

it is not your fault, it is just that manuals/tutorials don't tell much about streams. and don't worry, it took me a long time to understand streams. i just don't want people to encounter the same problems i had with them, that's why i always try to "demystify" streams.

Anyway the package authors cover about 350 lines with an procedure
example only using Streams, without ever saying why and when you should
sometimes choose Receive_Socket() and Send_Socket() in place of
Streams.

maybe because you just don't need them ! or only need them when you plainly understand what's behind them.

Thanks, it helped a lot to make me to understand Streams. I hope this
time I have been able to make myself clear. 

you already made yourself clear...

--
rien
.

Relevant Pages

  • Re: Convert from byte array to string
    ... i have no problem with the data sent to as400 socket, ... Ricardo Quintanilla G. ... >> the socket responds to me as a "byte array". ... >> then i need to convert the "byte array" into a string. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Convert from byte array to string
    ... > i have no problem with the data sent to as400 socket, ... > data received as response when i try to convert it from "byte array" to> string, ... >>> Ricardo Quintanilla G.>> ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Convert from byte array to string
    ... >i have a code that sends data to a socket listening over as400 platform,> the socket responds to me as a "byte array". ... > the problem is that the data converted from the byte array into a string>, ... > look at the last word, it have an accent, but when i convert it, the> accent ...
    (microsoft.public.dotnet.languages.csharp)
  • Convert from byte array to string
    ... the socket responds to me as a "byte array". ... then i need to convert the "byte array" into a string. ... look at the last word, it have an accent, but when i convert it, the accent ...
    (microsoft.public.dotnet.languages.csharp)
  • Help in French|Spanish|German translation.
    ... I am also an author of User-defined string functions. ... WORDTRANEX (cSearched, cArExpressionSought | cExpressionSough, ... each string of the array is searched ... If the parameter nArStartOccurrence is -1 or omitted, the replacement starts ...
    (microsoft.public.fox.helpwanted)