Do you mean instead of CF_LOWINIT and CF_HIGHINIT?
On Tue, May 12, 2009 at 3:20 PM, Mark Burgess wrote:
>
> Thanks.
>
> Would using these suffice to solve the issue?
___
Bug-cfengine mailing list
Bug-cfengine@cfengine.org
https://cfengine.org/mailman/li
Thanks.
Would using these suffice to solve the issue?
Matt Richards wrote:
> #define MAXINT ((int)~HIBITI)
> #define HIBITI ((int)-2147483648) /* (1 << BITS(int) - 1)*/
>
>
> On Tue, May 12, 2009 at 2:58 PM, Mark Burgess wrote:
>> What is the value or name of MAX_INT on AIX
#define MAXINT ((int)~HIBITI)
#define HIBITI ((int)-2147483648) /* (1 << BITS(int) - 1)*/
On Tue, May 12, 2009 at 2:58 PM, Mark Burgess wrote:
>
> What is the value or name of MAX_INT on AIX? I would rather make an
> exception in the header file than change the data type.
>
>
What is the value or name of MAX_INT on AIX? I would rather make an
exception in the header file than change the data type.
M
Matt Richards wrote:
> Greetings. I am still getting range overflow on AIX. The mtime value
> is too large to be a long.
>
> Validation: Int range item on rhs of lval 'm
Matt, this has been brought to my attention before, but I was
uncertain what to do. I don't want to change types to long long as
this introduced new problems on other systems.
Any other suggestions?
M
Matt Richards wrote:
> Greetings. I am still getting range overflow on AIX. The mtime value
>
Greetings. I am still getting range overflow on AIX. The mtime value
is too large to be a long.
Validation: Int range item on rhs of lval 'mtime' given as
{1210603176,1242052776 => 1210603176} is out of bounds (should be in
[0,2147483648])
Validation: Int range item on rhs of lval 'mtime' given as
