Last post by Lazybones - February 09, 2020, 01:27:55 PM
Hi all I have mcselector working on the current map, it doesn't all fit on one screen but I could visualize some of the differences.. Currently I have not been able to get entity filters to work but time inhabited seems to work perfectly.
Last post by Mr. Analog - February 04, 2020, 06:35:45 PM
Yeah there's a special place in hell for people who use exceptions for anything other than EXCEPTIONAL CONDITIONS likely the same mouth breathers who catch and eat an exception without logging or re-throwing - making debugging a royal pain.
Last post by Darren Dirt - February 04, 2020, 03:27:24 PM
That's where the debate kicks in to high gear.
Many suggest a single "pop up to the main loop" handling of virtually every "exception" but then you start using a framework that uses exceptions to identify non-critical fail conditions and errors and then ... ugh.
I think what the Python community does is smart, from what little I heard, and what miniscule of that I recall. Actually it might not even be Python, idk.
Cliffs(?) = Both sides are correct. Depending on [17 different aspects of your particular case]. ;-)
Personally I like how (for example) document.querySelectorAll returns an array always, so if no matches then you can just check if 0==returnedArray.length -- but then what about document.querySelector? Should it return null, or undefined? Or throw an error? Hmmm...
( tbh this YT convo is a nice single place offering a balanced summary of the pros and cons as provided by a bunch of different people with varying developer experience, unlike that mostly-one-sided journey of exploration I travelled 5 months ago researching checked vs unchecked exceptions in Java