kind of got side tracked away from the floating point stuff, but that's OK, I think recent work is worthwhile also.
I have a pull request cooking: fbc-tests Test Suite update Mar 2018
If anyone, it would affect St_W; I don't think many users ever really look at the test suite -- which is huge btw.
Here's a few of my thoughts, some related to this thread, some not.
What has been working well for me, is to get development from one usable state to the next usable state (with improvements), and having the calendar month be the time frame. It's not perfect, and seemingly never quite finished, however, seems like reasonable time frame to go from one working thing to the next working thing even if some work is going to be left for next update.
For the benefit of those that are not yet following the FreeBASIC project on github (you can create a login, follow projects, and subscribe to get updates sent to your email), the current issue is: I am confident the changes I have staged are good, but Travis-CI, whose purpose is to validate the changes, is not working correctly. Travis-CI is great; I love it. But what to do when it is not working? The "old way" was for a developer to just push changes to the main trunk and let others report the problems. aw, I was just having thoughts about "what did we do before Travis-CI?", well, we just had confidence that our changes were good, and if they weren't, expect other users to help report the problems.