< Previous by Date	Date Index	Next by Date >
< Previous in Thread	Thread Index

Re: [reSIProcate] dum compiler warnings

From: Scott Godin <sgodin@xxxxxxxxxxxxxxx>
Date: Fri, 29 Oct 2010 20:26:39 -0400

Thanks Kennard!

I've committed these fixes. For the dum test code, I just modified the tests to pass in a port of 0, to let the OS select the port instead of trying to use a random port like it was doing.

Scott

On Fri, Oct 29, 2010 at 5:03 PM, Kennard White <kennard_white@xxxxxxxxxxxx> wrote:

Hi,

My compiler (gcc44 on ubuntu) complains about some code in dum. Please see attached patch. I believe the lack of parens in the test code is actually a bug in that the code as written is not the behavior intended by the author, and this patch fixes it. But hard to know what the intent was.

Regards,
Kennard

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

References:
- [reSIProcate] dum compiler warnings
  - From: Kennard White

Prev by Date: Re: [reSIProcate] Forcing use particular Transport
Next by Date: Re: [reSIProcate] unresponsive DNS query blocks stack thread if USE_IPV6 is not defined (windows)
Previous by thread: [reSIProcate] dum compiler warnings
Next by thread: [reSIProcate] SipStack::send: clone vs new
Index(es):
- Date
- Thread