Quote - I'm not sure how you alpha test a program you only started typing.  Anyway, I've never heard of a bug that was hard to corner or squash.  A pet peeve I have are with programmers that aren't willing to or don't know how to clean up bugs in their own programs.  To me, if something is worth doing -- it's worth doing right.

Well, it wasn't at v0.1 - it was at v0.4 (v0.5 is where I start beta-testing).  And I had years of code all ready to be added and adjusted - or didn't you thoroughly test my posts before replying. ;)

Microsoft (the largest software company on the planet) sells plenty of software (and drivers and OSs) that doesn't appear to be 'fully beta-tested'.  Crashes and bugs and vulnerabilities everywhere.  What was that about a list of bugs that filled volumes?

Well, I'm glad that you're perfect.  You let me know when you've far surpassed my feeble attempt of the plugin that I wrote.  It only covers (various SDKs with different features and changes to the api interface) R8.2, R8.5, R9.1, R9.6, R10.0 (pending SDK docs) for Windows and MacOS and R9.1 Windows x64 - still working on the MacOSX UB version - as the zlib support there (which never failed me with my own compiles, fails me with the included and supposedly unaltered zlib included with MacOSX UB).  How do you debug someone else's lib again (there is no debug version afaik)?  In this case, I'm half-tempted to compile my own zlib as usual (bet it will work then!)

What exactly have you written that is of noteworthiness?

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone