Re: UnSigned Long
- From: Keith Thompson <kst-u@xxxxxxx>
- Date: Mon, 29 Aug 2005 23:05:53 GMT
"Mike Wahler" <mkwahler@xxxxxxxxxxxx> writes:
> "Emmanuel Delahaye" <emdel@xxxxxxxxxxxxxx> wrote in message
> news:mn.ed9b7d582d302c92.15512@xxxxxxxxxxxxxxxxx
>> Joriveek wrote on 29/08/05 :
>>> I want to store myvarz = 3000000000;
>>>
>>> I have declared myvarz as unsigned long; still not taking.
>>>
>>> I am using MSVC++ 6.0
>>
>> Check your ULONG_MAX (in <limits.h>) It could be not big enough for the
>> value you want.
>
> It is large enough. I suspect OP didn't tell us the
> whole story.
He certainly didn't. The above is all the information the OP gave us,
except for the "Any help please urgent...." at the end of the article.
There's no reason to think he can't store the value 3000000000 in an
unsigned long, and no clue what he means by "still not taking".
If it's really urgent, presumably he'll be following this thread and
will jump in any moment with a clearer explanation of what he's asking
for. Until then, there's really no point in speculating.
I'm tempted to suggest that if somebody posts an unclear question, and
somebody else has posted a followup asking for clarification, we
should drop the thread. Unfortunately there doesn't seem to be any
good way to drop a thread.
To any newbies reading this:
If you're having a problem, please give us the information we need to
help you solve it. I understand that it's hard to know just what
information is needed, so sometimes we'll need to go back and forth a
couple of times. Some hints:
Provide a small complete (compilable and executable) program that
exhibits the problem. The "compilable and executable" part is
optional if the problem is that it won't compile or execute.
Don't use any system-specific headers. If you need them to
illustrate the problem, you need to post to a system-specific
newsgroup. If you don't know which headers are system-specific,
we'll be glad to offer advice. (We're sometimes a bit
over-sensitive about topicality, so be patient.)
Tell us what you expect the code to do and what it actually does.
If you get error messages, show them to us. Cut-and-paste both
the code and the error messages; don't try to summarize or re-type
them.
If your problem description is equivalent to "It doesn't work",
you're not giving us enough information.
These are not arbitrary rules; they're ways you can help us to help
you. Any extra time they cost you will be more than paid back in the
speed with which we can either give you an answer to tell you where to
find the people who can.
--
Keith Thompson (The_Other_Keith) kst-u@xxxxxxx <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.
.
- References:
- UnSigned Long
- From: Joriveek
- Re: UnSigned Long
- From: Mike Wahler
- UnSigned Long
- Prev by Date: Re: while (1) vs. for ( ;; )
- Next by Date: Re: while (1) vs. for ( ;; )
- Previous by thread: Re: UnSigned Long
- Index(es):
Relevant Pages
|
