It's just what I decided to go with for myself, to help me keep things separate.
QB64 doesn't care about your extension. In the end, it only works with TXT files, though you can name them however you want.
The standard convention has always been:
*.BAS for a QB64 program.
*.BI for library code that goes at the beginning in a program.
*.BM for library code that goes at the end of a program.
Since v 4.4.0 makes those split libraries unnecessary, I've just decided to use *.QLB for my own personal libraries so I can tell at a glance -- "This is a combined, full library with both declares and subs/functions all included in the single file."
Honestly, it'd be nice if others adopted such a convention as well, but for now, I think this is just a "Steve Thing". Though fingers are crossed that it might hopefully catch on with others as well, rather than them just making *.BI files with subs in them, which might confuse folks with older versions of QB64 who see them and make them think they'll work for them as well.
QB64 doesn't care about your extension. In the end, it only works with TXT files, though you can name them however you want.
The standard convention has always been:
*.BAS for a QB64 program.
*.BI for library code that goes at the beginning in a program.
*.BM for library code that goes at the end of a program.
Since v 4.4.0 makes those split libraries unnecessary, I've just decided to use *.QLB for my own personal libraries so I can tell at a glance -- "This is a combined, full library with both declares and subs/functions all included in the single file."
Honestly, it'd be nice if others adopted such a convention as well, but for now, I think this is just a "Steve Thing". Though fingers are crossed that it might hopefully catch on with others as well, rather than them just making *.BI files with subs in them, which might confuse folks with older versions of QB64 who see them and make them think they'll work for them as well.