Dennis E. Hamilton

@raysan5 @krisvers > @krisvers Simbol collisions can already be avoided. I can consider slightly renaming some functions added 6 months ago but not the full library. If anyone really has...

@krisvers > However, a prefix for this project should have been from day one especially with many function names being the same as in other mainstream libraries like the winapi....

@luis605 I agree that the name should reflect what is actually determined. On the other hand, I am unclear what the user action is expected to be on !Is\*Valid and...

@luis605 > It would also be nice for this functions to have a logging mechanism to alert the developer/user what the problem is, so he/she can further troubleshoot. I can't...

@planetis-m > Not to say that I could still be wrong, but please to advance the conversation, try to show me actual breakage, it's only fair to ask as I...

@planetis-m @raysan5 > > There's a mismatch with very small numbers: > > ``` > Mismatch: > v: (7.91498e-24, 2.17773e-32) > result1: (0, 0) > result2: (7.91498e-24, 2.17773e-32) > ```...

@JayLCypher @planetis-m @raysan5 Let's review the bidding here. I believe there are three factors to consider. 1. The prospect of floating-point exceptions should simply be avoided, although overflows might be...

I don't think "Valid" is an appropriate replacement for "Ready." Not being Valid tends to be understood as a failure case. There are alternatives, but since these renames are not...

I confirm that the problem still exists in 6.2.0, getting the OpenLiveWriter 404 page asking for a report of the failing URL. There is apparently a redirect that lands at...