06-14-2022, 02:00 AM
> My impression was the appraoch to QB64 has been to keep the new parts to a minimum, to accommdate newer features of PCs since the old days.
Considering the current feature set of QB64 the cat might be out of the bag on that one
Though that might not be completely fair.
I haven't really thought about adding new operators, but I can say that it would be a lot messier than adding new functions (as was done for
> 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.
Considering the current feature set of QB64 the cat might be out of the bag on that one
Though that might not be completely fair.I haven't really thought about adding new operators, but I can say that it would be a lot messier than adding new functions (as was done for
_SHR, I guess). I think there's also an important distinction to be made because some things like
_SHRcan be implemented as regular functions, but things like
AndAlsocannot be implemented as a regular function, so an operator is just about necessary for them (or it would be something that looks like a function, but doesn't actually work like one).
> 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.