The fact that an Axe source file starting with two periods (a subprogram/library) doesn't show up in the compile menu is intentional. That way, you don't have subprograms and libraries cluttering up the compile menu, since it doesn't make sense to compile either as a standalone executable.


Just include prgmLIBNAME as a line in your main program and the library will be included and compiled with your main program.

Other than showing up in the compile menu or not, there's no inherent difference between an Axe source file that starts with one or two periods. There's nothing stopping you from using a source program that starts with one period as a subprogram or library, and if the compile menu didn't explicitly hide source files that start with two periods, you could compile those as main programs.

One important thing to keep in mind about this lack of differentiation is possible unexpected behavior in a case like the following:

:.TEST
:SayHello()
:
:prgmSUB
:..
:Lbl SayHello
:Disp "Hello world!"
:Return

The execution path will, after the initial SayHello() is reached, mosey right on into prgmSUB and repeat it, due to there being no Return or other control block to stop it. So if you don't want execution to run into your subprogram/library, it's a good idea to make sure that you either include it in a place where you know execution won't naturally reach, or to make sure that your subprogram/library wraps its code in a block that will skip its execution, like If 0 ... End or Goto SubEnd ... Lbl SubEnd.

Also, a slight note: there are two quirks about inclusion of subprograms/libraries that come to mind. The first quirk is that you cannot include a subprogram/library from another subprogram/library (yet?). And the second quirk is that any changes a subprogram/library makes to the optimization target (size versus speed) will be reverted to the main program's settings when the subprogram/library is done being compiled.

Oh... ok well im off to work on my first lib! Wish me luck!

Possible reasons of why it would quit instead of return to main execution :

• You use Return^r instead of Return at the end of the subroutine.
• You do Goto Subroutine instead of Subroutine().

You can use whatever  variable or function within a subroutine. It'll be easier if you just post your code.

:.header
:prgmLIB
:ACT()
:other code

:.LIBSRC
:Lbl ACT
:r1->strg111
:Return

This doesnt work!!!

Well I was kinda right about the cause of the problem. And that's what Runer said when he wrote "make sure that you either include it in a place where you know execution won't naturally reach, or to make sure that your subprogram/library wraps its code in a block that will skip its execution, like If 0 ... End or Goto SubEnd ... Lbl SubEnd."

prgmLIB should be at the bottom of your source. Don't put a return in the end of it, but in the beginning. Also it should start with "..", not ".", although that's not the problem.


Like so :

Code: [Select]

:.header
:ACT()
:other code
:prgmLIB


:..
:Return
:Lbl ACT
:r1->strg111

I'd advise more to put the Return in the main program for more visibility. I just like to know where my program ends.

I am against using subprograms anyway, except for huge projects. You said it yourself in the zStart topic, you're wasting time swapping between your files, time that you could save if everything was at the same place. And you would not have problems being lost thanks to zStart's label menu. But whatever fits you I guess.