The tcc22 announcement states: "We added library functions to TCC. Library function syntax is similar to batch files, but they're loaded into RAM and called as if they are internal commands. This allows very fast common subroutines, or a powerful multi-line alias capability."
What I do understand is the part about library being less tiresome than multi-line aliases. I'm wondering about the "very fast" part - esp. in comparison to btm files which are loaded into RAM too, aren't they? And how about the possibility to call a batch file from a library function?
Or are libraries the replacement for the crawling speed of GOSUB, which needs to search through the whole batch file to find the matching :function marker? If so, it would be convenient if inline library functions could be read from the top of a batch file and then auto-discarded after the batch file is finished.
What I do understand is the part about library being less tiresome than multi-line aliases. I'm wondering about the "very fast" part - esp. in comparison to btm files which are loaded into RAM too, aren't they? And how about the possibility to call a batch file from a library function?
Or are libraries the replacement for the crawling speed of GOSUB, which needs to search through the whole batch file to find the matching :function marker? If so, it would be convenient if inline library functions could be read from the top of a batch file and then auto-discarded after the batch file is finished.