What it means is that your flags are going past what they can, for example,
going past 32 (31?) bits in an unsigned long int. You can move to unsigned
long long, but that will corrupt binary pfiles and you'll have to change all
your flag defintions from
#define SOME_FLAG (1 << x)
to
#define SOME_FLAG (1ULL << x)
That could very well be the problem, because I think (1 << 32) or (1 << 33)
becomes (1 << 1), then the next becomes (1 << 2), so it goes back over. In
other words, they would be the same flag.
Something like that.
-k.
-----Original Message-----
From: Circle Discussion List [mailto:CIRCLE@post.queensu.ca]On Behalf Of
Shaun Bourque
Sent: Saturday, May 29, 1999 10:44 AM
To: CIRCLE@post.queensu.ca
Subject: Re: [NEWBIE] !class flags on objects
my invalid_class looks fine. i have a warning when compiling now that says:
in function 'invalid_race'
left shift count >= width of type
i didnt realize i had that error, would that mess up the !classes? and if so
how do i fix that. thanks.
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST