Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #11065
| From | "A" <a@a.a> |
|---|---|
| Newsgroups | comp.lang.c++ |
| Subject | Re: Limiting function input only to __int64 but not int... |
| Date | 2011-10-24 17:11 +0200 |
| Organization | B.net Hrvatska d.o.o. |
| Message-ID | <j83v8f$g91$1@gregory.bnet.hr> (permalink) |
| References | <j824fk$5bf$1@gregory.bnet.hr> <c59f1d33-57bf-47f9-b23a-90cfff62c8c3@f36g2000vbm.googlegroups.com> |
"Goran" <goran.pusic@gmail.com> wrote in message news:c59f1d33-57bf-47f9-b23a-90cfff62c8c3@f36g2000vbm.googlegroups.com... >Out of curiosity... Why? int "is an" __int64 any way you look at this. >Why would it matter? because function requires explicitly __int64 because ID's are 64-bit, providing 32-bit int would ruin ID's that go over the 32-bit boundary. This may happen when I do text-to-int conversions using StrToInt and forget to put StrToInt64 instead. In Borlangearcadero C++ Builder 2010 which I use, these functions output int and __int64 so compiler SHOULD be able to check these but unfortunately it doesn't - even if I enable W8102 Implicit conversion of '%s' to '%s' (C++) but it doesn't do what it is supposed to. I tried casting to wrong type but the warning is still not triggered.
Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Limiting function input only to __int64 but not int... "A" <a@a.a> - 2011-10-24 00:28 +0200
Re: Limiting function input only to __int64 but not int... Ian Collins <ian-news@hotmail.com> - 2011-10-24 11:49 +1300
Re: Limiting function input only to __int64 but not int... Juha Nieminen <nospam@thanks.invalid> - 2011-10-24 08:08 +0000
Re: Limiting function input only to __int64 but not int... yatremblay@bel1lin202.(none) (Yannick Tremblay) - 2011-10-24 14:24 +0000
Re: Limiting function input only to __int64 but not int... Marc <marc.glisse@gmail.com> - 2011-10-23 22:52 +0000
Re: Limiting function input only to __int64 but not int... "A" <a@a.a> - 2011-10-24 01:32 +0200
Re: Limiting function input only to __int64 but not int... Goran <goran.pusic@gmail.com> - 2011-10-23 23:29 -0700
Re: Limiting function input only to __int64 but not int... "A" <a@a.a> - 2011-10-24 17:11 +0200
Re: Limiting function input only to __int64 but not int... Robert Wessel <robertwessel2@yahoo.com> - 2011-10-24 12:17 -0500
Re: Limiting function input only to __int64 but not int... Richard Damon <news.x.richarddamon@xoxy.net> - 2011-10-24 13:49 -0400
Re: Limiting function input only to __int64 but not int... "A" <a@a.a> - 2011-10-25 00:12 +0200
Re: Limiting function input only to __int64 but not int... Richard Damon <news.x.richarddamon@xoxy.net> - 2011-10-24 20:20 -0400
Re: Limiting function input only to __int64 but not int... Christian Gollwitzer <auriocus@gmx.de> - 2011-10-25 07:27 +0200
Re: Limiting function input only to __int64 but not int... Arne Mertz <arnemertz@googlemail.com> - 2011-10-26 01:02 -0700
Re: Limiting function input only to __int64 but not int... Marcel Müller <news.5.maazl@spamgourmet.com> - 2011-10-24 09:18 +0200
Re: Limiting function input only to __int64 but not int... Ian Collins <ian-news@hotmail.com> - 2011-10-24 20:53 +1300
Re: Limiting function input only to __int64 but not int... Ian Collins <ian-news@hotmail.com> - 2011-10-24 20:58 +1300
csiph-web