[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[sr #107822] Testing 3.0.2 on AIX

From: Bjørn Christensen
Subject: [sr #107822] Testing 3.0.2 on AIX
Date: Fri, 30 Sep 2011 10:15:56 +0000
User-agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30618; .NET4.0C)

Follow-up Comment #13, sr #107822 (project gnutls):

If I could choose I would try to program more defensive!

First I would define RESUME_FALSE 0 because that is what I would expect from

Also that would if calloc'ed buffer is used default would be not resuming.

Then I would make all comparisons session->internals.resumed == RESUME_FALSE
or session->internals.resumed != RESUME_FALSE 

agains the value defined as 0. In your case RESUME_TRUE, if suggested above

In K&R they state that the behaviour of bit fields are implementation
specefic. (Code Defensive)

Does that make any sense?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]