08-16-2023, 09:50 PM
As long as we're wishing...
@SMcNeill @a740g @offbyone I asked this in private already, but would like to share this here.
Are there plans to evolve the language further with things like...
These things are so nice in other languages, I'm finding I'm really missing them.
The issue isn't that QB64PE isn't like every other language - it can be it's own thing, the issue is I'm building bad habits.
GOSUB and GOTO lol - Nothing wrong with them they work fine, but the reason I used those recently is because it's so cumbersome to pass variables around elegantly. The language isn't DRY (Don't Repeat Yourself) at all.
So instead of shimming everything into funcs and subs where i am now using gosub and goto, i just move on with life.
Meanwhile my cognitive load is higher than it should be in QB64 vs. other languages.
Anyway
Just some thoughts
There are work-arounds for 1, 4, 8, 9, and 10, I know, but having to work-around shouldn't be required, IMO.
QB64PE has taken the approach of evolution, making things better, etc.
These few things wouldn't really be drastically changing anything unless someone wanted to use them (read: users of newer languages contemporary in the modern work force)
I don't know the way it's written underneath the hood, but do you guys have a roadmap or a vision?
If not, why not? what are the goals of QB64PE project?
Thanks for reading ?
@SMcNeill @a740g @offbyone I asked this in private already, but would like to share this here.
Are there plans to evolve the language further with things like...
- Native BOOL _TRUE and _FALSE (maybe using '$:BOOL to make it optional)
- Optional parameters for SUBs and FUNCTIONs
- EVAL("QB CODE")
- Returning arrays from SUBs and FUNCTIONs
- Arrays inside UDTs
- Arrays of UDTs inside UDTs
- Passing FUNCTIONs and SUBs into other FUNCTIONs and SUBs
- '$INCLUDE_ONCE:
- Native JSON ('$JSON)
- Native DICTIONARY ('$DICTIONARY)
- FUNCTIONs and SUBs inside other FUNCTIONs and SUBs
These things are so nice in other languages, I'm finding I'm really missing them.
The issue isn't that QB64PE isn't like every other language - it can be it's own thing, the issue is I'm building bad habits.
GOSUB and GOTO lol - Nothing wrong with them they work fine, but the reason I used those recently is because it's so cumbersome to pass variables around elegantly. The language isn't DRY (Don't Repeat Yourself) at all.
So instead of shimming everything into funcs and subs where i am now using gosub and goto, i just move on with life.
Meanwhile my cognitive load is higher than it should be in QB64 vs. other languages.
Anyway
Just some thoughts
There are work-arounds for 1, 4, 8, 9, and 10, I know, but having to work-around shouldn't be required, IMO.
QB64PE has taken the approach of evolution, making things better, etc.
These few things wouldn't really be drastically changing anything unless someone wanted to use them (read: users of newer languages contemporary in the modern work force)
I don't know the way it's written underneath the hood, but do you guys have a roadmap or a vision?
If not, why not? what are the goals of QB64PE project?
Thanks for reading ?