Leaderboard

When compiling, a vlx file and fas files are created. the fas file is created for each lsp file, and the vlx file contains all lsp files within it. compiling multiple lsp files into vlx does not mean that each lsp file remains inside of vlx file system automatically optimizes them and combines them into one code file. like mhupps lsp code. so you cannot load them with (load "xxx.lsp"), If a file with the same name does not exist in that path... so you can choose between loading a single vlx file or multiple fas files. no need to load both vlx, fas, (of course no need to load already compiled lsp files It is already loaded when you load vlx.) but, it is no longer the 'main loader'. because when vlx file loaded, all its functions on the system at once. the main reason for using this feature is in old PCs, the lsp file loaded like this had a impact on speed. so i think, changing the order is not affect to that situation. (unless it is an lsp file that calls itself without inputting command) i think the error has been resolved simply by removing the (load "~~~.lsp") statement.

You are correct, order doesn't matter, I checked it after reading your post. My goal was to "combine" .lsp subfunctions into a single file (which doesn't have readable code to third users) such that when I need a subfunction from fileA.lsp and another from fileB.lsp (fileA and fileB have tens of subfuctions that maybe change in the future) I just "import" them from there. And when I change my subfunction in fileA.lsp I don't have to go to the "merged" .lsp and manually copy/paste the new function. Thank you both for your time.

Hi martinle unfortunately, I am not that experienced either, hopefully other group members could help you?