🚀 go-pugleaf

> The answer to the original question, though, depends very much on the
> environment supplied with the compiler.  The obvious solution is
> to have three files:
>     STACK.DEF
>               starts with "DEFINITION MODULE Stack;"
>     STACK1.MOD
>               starts with "IMPLEMENTATION MODULE Stack;"
>     STACK2.MOD
>               starts with "IMPLEMENTATION MODULE Stack;"
> 
> ...

> Now that I've started using TopSpeed M2, the whole structure collapses,
> for two reasons:

It is indeed a nuisance.

(*# pragma(implementation=>off) *)

and use explicit project file link with the relevant precompiled 
implementation modules might work but I haven't tried it. This is after all 
how people operate who do not possess the library source.

Further pragmas and project file directives can sort out all sort of horrid 
problems eg. a program which uses multi-language and third party libraries can 
be done. 

I find that I am increasingly using complex project files where the 
do-it-fo-you cannot work.

The documentation doesn't seem to help eg. some of the C compatibility 
directives did not work, nothing happened and no error msgs. Worked just fine 
when placed in the definition file! Obvious in hindsight.
Try experimenting with the underscore directive.

There is also the method using conditional compilation. Look at the assembler 
lib source for lots of examples.

>  (b) the TopSpeed system won't even accept the file names I used above,
>      since it requires a match between the source file name and the module
>      name (rather than the more logical approach of requiring a match
>      between the module name and the symbol file name).

I like this.

  TC. 
    E-mail: tchannon@black.demon.co.uk or tchannon@cix.compulink.co.uk