On 5/23/06, Cory Nelson <[EMAIL PROTECTED]> wrote:
> I'm not fully sure about this as I never had to do any programming for
> 64 bits, yet, so correct me if I'm wrong.
GCC's int is also 32bit on x64 (likely because x64 supports 32bit
arithmetic in 64bit apps without penalty, while 64bit operatio
On 5/23/06, Craig Morrison <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
> If you do not care to see the warnings, there is probably
> some way to turn them off in your compiler.
To the OP:
In VC7 and above.. Open the project settings for your project, navigate
to: Configuration Propertie
[EMAIL PROTECTED] wrote:
If you do not care to see the warnings, there is probably
some way to turn them off in your compiler.
To the OP:
In VC7 and above.. Open the project settings for your project, navigate
to: Configuration Properties -> C/C++ -> Disable Specific Warnings. Plug
in the wa
"Cory Nelson" <[EMAIL PROTECTED]> wrote:
>
> To get back on track: Brannon, submit a patch. An alarmingly high
> number of people believe those warnings are superfluous and from what
> I understand drh is one of them, so I imagine a patch is the only way
> proper casting will be put in.
>
Even
On 5/22/06, Nuno Lucas <[EMAIL PROTECTED]> wrote:
On 5/22/06, Cory Nelson <[EMAIL PROTECTED]> wrote:
> The warning is likely because size_t can be 64bit and "int" is always
> 32bit. Either way, it should be casted.
Not really, size_t can be 64 or any other size in bits and same with int's.
H
On 5/22/06, Cory Nelson <[EMAIL PROTECTED]> wrote:
The warning is likely because size_t can be 64bit and "int" is always
32bit. Either way, it should be casted.
Not really, size_t can be 64 or any other size in bits and same with int's.
If I'm not mistaken, size_t is 64 bits on Microsoft 64
On 5/22/06, Jay Sprenkle <[EMAIL PROTECTED]> wrote:
On 5/22/06, Brannon King <[EMAIL PROTECTED]> wrote:
> Is the number of size conversion warnings during sqlite compile
> disconcerting to anyone but myself? I've attached a log of them below. I
> vdbemem.c
> vdbemem.c(194) : warning C4267: '=' :
This is pretty much a bogus warning since in windows size_t is an integer:
size_t should always be unsigned. ssize_t is the signed variant.
Roger
On 5/22/06, Brannon King <[EMAIL PROTECTED]> wrote:
Is the number of size conversion warnings during sqlite compile
disconcerting to anyone but myself? I've attached a log of them below. I
vdbemem.c
vdbemem.c(194) : warning C4267: '=' : conversion from 'size_t' to 'int',
possible loss of data
Is the number of size conversion warnings during sqlite compile
disconcerting to anyone but myself? I've attached a log of them below. I
want to know that when I compile this on a 64 bit system none of my memory
pointers get truncated. And visa-versa with the file pointers. If we are
using a 32bit
10 matches
Mail list logo
