[Devel] setflag and isflagset functions don't represent full range of flags available

Bogdan-Andrei Iancu bogdan at voice-system.ro
Wed Aug 2 14:40:29 CEST 2006


Hi Tavis,

For some historical reasons (not to say unknown), the flag 0 is consider 
out of range, even if there is no reason to do so.
On a 32 bits arch, the range will be 0-31.
On a 64 bits arch, the range is 0-63.

I will enable to usage of flag 0 on the cvs devel version.

regards,
bogdan

Tavis P wrote:

>Sorry, this is in a recent cvs checkout of 1.0.0 (two weeks ago)
>
>Tavis P wrote:
>  
>
>>I'm trying to make use of flag value 0 ( isflagset(0) ), and an error is
>>generated
>>
>>The dokuwiki indicates that the valid range of values is 0..31
>>(http://www.openser.org/dokuwiki/doku.php?id=openser_core_cookbook&DokuWiki=cae11d2ccfdd1cb73f3f4359d0b1d921#isflagset_int)
>>
>>Also, the tm module parameter "branch_flag_mask" indicates that there
>>are 32 possible values
>>---
>>modparam("tm", "branch_flag_mask", "b00000000000000000000000000010110")
>>---
>>
>>Perhaps the isflagset and setflag functions are mistaken?
>>
>>
>>This is the error generated when trying to use "isflagset(0)"
>>---
>>ERROR: message flag (0) must be in range 1..31
>>---
>>
>>tavis
>>
>>_______________________________________________
>>Devel mailing list
>>Devel at openser.org
>>http://openser.org/cgi-bin/mailman/listinfo/devel
>>
>>
>>  
>>    
>>
>
>
>_______________________________________________
>Devel mailing list
>Devel at openser.org
>http://openser.org/cgi-bin/mailman/listinfo/devel
>
>  
>




More information about the Devel mailing list