Re: Question on select() and sockets

On Jun 10, 6:32 am, Rainer Weikusat <rweiku...@xxxxxxxxxxx> wrote:
David Schwartz <dav...@xxxxxxxxxxxxx> writes:
On Jun 10, 5:05 am, Rainer Weikusat <rweiku...@xxxxxxxxxxx> wrote:
In other words, a UDP datagram can be dropped at any time.

And this is wrong. If a UDP datagram is lost in transport for some
reason, it is the responsibility of the application to cope with that.
That's all what the protocol definition (of IP, actually) says to
this.

Umm, how's it wrong?

It will not be possible to explain this to someone who cannot
immediatly see the difference between both statement. So, please,
believe whatever you want and let us leave it that way.

You are the one making the positive claim. You claim that some
standard prohibits this behavior.

I am making a negative claim. I claim this behavior violates no
standard. I make this claim both because I have searched the standards
and because I have challenged others to cite the standard it violates.

If you discarding a UDP datagram after receipt violates some standard,
it should be simple enough to cite the standard that it violates. Yet
you don't seem to be willing to this.

Obviously, I can't cite the thing it doesn't violate.

DS
.

Relevant Pages

  • Re: C Strings not returning from a function
    ... Constraint violation. ... I'm not so sure the standard specifies ... what the effect of the implicit declaration of mallocis. ... what violates a constraint. ...
    (comp.lang.c)
  • Re: Does a constraint violation imply undefined behavior?
    ... just because a constraint has been violated. ... But if a program violates enough constraints, ... I pointed to the requirement for conforming implementations to accept ... Unless the standard places such requirements on the implementation. ...
    (comp.std.c)
  • Re: Is Fortran a legal system or religion? (was: Re: Hardware issues [Re: Floating point required ex
    ... Fortran in permissive. ... >> a program violates the standard, the implementation may do as it ... if you *say* your program conforms to ... some standard, your are legally *required* to stand by that statement ...
    (comp.lang.fortran)
  • Re: FFTW and ifort
    ... >> matter how they are changed. ... Glen's statement as a general caveat that mixing Fortran and C ... it is possible to write C code that violates this. ... that would violate the Fortran standard. ...
    (comp.lang.fortran)
  • Re: Fortran Features
    ... Any other action violates the ... standard. ... constraints. ... no deficiencies and the other way is to make it so complicated ...
    (comp.lang.fortran)