lotus



previous page: C11.2) Bugs in version 5.1 of the compiler
  
page up: BETA Programming Language FAQ
  
next page: C11.2.2) Other undefined entries (compiler import error)

C11.2.1) "T1PROGRAM undefined" still reported by the linker




Description

This article is from the FAQ, by with numerous contributions by others.

C11.2.1) "T1PROGRAM undefined" still reported by the linker

As mentioned in C11.1.3, version 5.1 of the compiler partly fixes the
problem of "T1PROGRAM undefined". To be specific, v5.1 of the compiler
checks, that the PROGRAM slot is met before initiating a call to the linker.

However, it may fail as follows:

beta frag1 frag2

if frag1 contains a PROGRAM slot, and frag2 does not, you will get the
linker error for frag2: Once a PROGRAM slot has been seen, all fragments
subsequently translated will be attempted linked. This error also happens if
you invoke the compiler as

beta -r frag1

and then enters frag2 as second fragment to compile when the repeating
compiler asks for it.

Also, if you have declared a Dopart- or Descriptor-slot in one of your
files, and do not have a fragment, that binds these slots in any of the
files in the dependency graph, then the linker may still fail with an
undefined entry for this slot.

See also C11.2.2.

 

Continue to:















TOP
previous page: C11.2) Bugs in version 5.1 of the compiler
  
page up: BETA Programming Language FAQ
  
next page: C11.2.2) Other undefined entries (compiler import error)