X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Tue, 5 Jan 2016 16:51:17 -0500 Message-Id: <201601052151.u05LpHrp007414@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: (geda-user AT delorie DOT com) Subject: Re: [geda-user] Re: some more geometry module tweaks (sorry, wall of text) References: Reply-To: geda-user AT delorie DOT com > I agree, but we may have different ideas of what the fix would be. If you > want to stop using floating point entirely, it's a huge effort, and ints > won't do what you want either, you need rationals. We use nanometers, I think that's as fixed-point as we need to get :-) It would be rare to have a valid case where a floating format is preferable to non-overflowing nanometers. > My claim on this is that if your float type entirely contains the set of > your int type, there's no doubt about how the conversion in one direction > should work. But using a floating type means you can ignore overflow issues and the loss of precision therein.