(06-14-2022, 02:00 AM)DSMan195276 Wrote: > I would say that if we are going to add stuff to the language, keep it to important changes, like
Personally (and this is me just making this up) I think it would be good to have a clearer distinction between "core" features that are part of the language, and add-on type things that are basically just special libraries. Things like arrays in UDTs would definitely be a "core" feature (and one I would like to see), things like GUI support in the language would be better served more as a separate thing you can pull-in (even if it had special language support to make it nicer to use). Maintaining stability for something like a full GUI library is a whole different can of worms, and could reasonably get replaced by something better in the future even if we keep the old one supported.
All that makes sense and I pretty much agree.
What is AndAlso supposed to do anyway, that can't be done with normal if then else elseif ?
Is it something like "finally" in a try catch block?
(I never saw the point in "finally" as well.)
But speaking of try/catch and if we're talking making improvements, how about adding improved error handling? As is, QB64's ON ERROR GOTO is awfully limited - you can't even GOTO a line inside a function, it has to be a label defined somewhere in the main code. What we need is ON ERROR RESUME NEXT that works like it does in VBA, or a simple TRY/CATCH. I've been living without it for the 2+ years since I've dove into QB64, but improving the scope of error handling would be a nice upgrade!