ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Yeah, it does, once you reach the limit, although admittedly it is quite a few decimal places, 0.9999999999999999 or whatever amount, I guess it just depends on what they're doing or whatever size of numbers they'll be dealing with, either way, they've got two suggestions now so....
as you can see iPart is always the integer part of num, it doesnt round, however 9.99999... does eventually round to 10.0, i think this is what led you to your conclusion that typecasting to an int rounds but as you can see it doesnt.
everbody needs help sometimes, took me 3 minutes to write that program then over an hour to compile/run it
So what's happening is when the type reaches it's precision limit for it's size it's been rounded up because of that not because of casting?
looking again my overblown way would have suffered from the exact thing it was trying to prevent because it parsed back into a number.
your method would suffer like mine but it would be due to the fact that number would be rounded up at the point you set it, which is obviosly before you convert it into a string. however your method is slightly more accurate than mine because i subtract and hence introduce numerical errors, you method has no loss of accuracy at all.
Another little bit of insight gleemed from the LQ boards