@Eros or @Petr: When should I use the .tbasicu file extension instead of the normal .tbasic one?
Printable View
@Eros or @Petr: When should I use the .tbasicu file extension instead of the normal .tbasic one?
eh ...
Better Petr will reply, it was his invention :D
In any case i think tbasicu stands for thinBasic UNIT that is an include file auto sufficient that means it has no external reference and can be re-used in different situations.
So it hasn't really any functionality behind it?
So far not other than thinAir/thinBasic will not execute them directly.
Having a kind of UNIT/Single/independent piece of code that can become a library is not bad
Maybe something for future.
I know Petr is using such file very often and is not bad at all. Every tbasicu can be considered "portable" in other projects.
Thanks Eros for the explanation. That is good enough for me.
Basically,
.tbasicU files contain functions with implementation and or types (with type functions or without).
.tbasicI files I use then for declares of DLL functions, for example.
Petr
Thanks Petr, good to know.