Re: [Warning] converting to `unsigned int' from `double';

* er:


You shouldn't use 'unsigned' for other than bit level manipulation.

The standard library does, for historical reasons, and it sucks.

Ignoring that very good advice (which if you're a smart man is what you should
pay heed to), to just get rid of the warning (brainless dog's or copy-cat's
solution),

   unsigned const n = unsigned( 5e4 );

One reply else-thread recommends static_cast. In this context using static_cast
is meaningless, for there's no chance at all that the type involved will change.
But using unsigned is of course infinitely more silly, so just don't do it.

Another reply else-thread suggests that 5e4 may not exactly represent 50000 on
all C++ implementations. But there's no need to be concerned about that: no
actually used floating point representation fails to represent 50000 exactly,
and no future floating point representation will fail. On the other hand, do
think about doing things like

   int const n = 50*1000;

Cheers & hth.,

- Alf