[next] [prev] [prev-tail] [tail] [up]

### C.6 Code generator messages

This section lists all messages that can be displayed if the code generator encounters an error condition.

Error: Parameter list size exceeds 65535 bytes
  The I386 processor limits the parameter list to 65535 bytes. (The RET instruction causes this.)
Error: File types must be var parameters
  You cannot specify files as value parameters, i.e., they must always be declared var parameters.
Error: The use of a far pointer isn’t allowed there
  Free Pascal doesn’t support far pointers, so you cannot take the address of an expression which has a far reference as a result. The mem construct has a far reference as a result, so the following code will produce this error:
  var p : pointer;
  ...
  p:=@mem[a000:000];

Error: EXPORT declared functions can’t be called
  No longer in use.
Warning: Possible illegal call of constructor or destructor
  The compiler detected that a constructor or destructor is called within a a method. This will probably lead to problems, since constructors / destructors require parameters on entry.
Note: Inefficient code
  Your statement seems dubious to the compiler.
Warning: unreachable code
  You specified a construct which will never be executed. Example:
  while false do
  begin
  {.. code ...}
  end;

Error: Abstract methods can’t be called directly
  You cannot call an abstract method directly. Instead, you must call an overriding child method, because an abstract method isn’t implemented.
Register arg1 weight arg2 arg3
  Debugging message. Shown when the compiler considers a variable for keeping in the registers.
Stack frame is omitted
  Some procedure/functions do not need a complete stack-frame, so it is omitted. This message will be displayed when the -vd switch is used.
Error: Object or class methods can’t be inline.
  You cannot have inlined object methods.
Error: Procvar calls cannot be inline.
  A procedure with a procedural variable call cannot be inlined.
Error: No code for inline procedure stored
  The compiler couldn’t store code for the inline procedure.
Error: Element zero of an ansi/wide- or longstring can’t be accessed, use (set)length instead
  You should use setlength to set the length of an ansi/wide/longstring and length to get the length of such string type.
Error: Constructors or destructors cannot be called inside a ’with’ clause
  Inside a with clause you cannot call a constructor or destructor for the object you have in the with clause.
Error: Cannot call message handler methods directly
  A message method handler method cannot be called directly if it contains an explicit Self argument.
Error: Jump in or outside of an exception block
  It is not allowed to jump in or outside of an exception block like try..finally..end;. For example, the following code will produce this error:
  label 1;
  ...
  try
  if not(final) then
  goto 1; // this line will cause an error
  finally
  ...
  end;
  1:
  ...

Error: Control flow statements aren’t allowed in a finally block
  It isn’t allowed to use the control flow statements break, continue and exit inside a finally statement. The following example shows the problem:
  ...
  try
  p;
  finally
  ...
  exit; // This exit ISN’T allowed
  end;
  ...

  If the procedure p raises an exception the finally block is executed. If the execution reaches the exit, it’s unclear what to do: exit the procedure or search for another exception handler.

Warning: Parameters size exceeds limit for certain cpu’s
  This indicates that you are declaring more than 64K of parameters, which might not be supported on other processor targets.
Warning: Local variable size exceed limit for certain cpu’s
  This indicates that you are declaring more than 32K of local variables, which might not be supported on other processor targets.
Error: Local variables size exceeds supported limit
  This indicates that you are declaring more than 32K of local variables, which is not supported by this processor.
Error: BREAK not allowed
  You’re trying to use break outside a loop construction.
Error: CONTINUE not allowed
  You’re trying to use continue outside a loop construction.
Fatal: Unknown compilerproc ”arg1”. Check if you use the correct run time library.
  The compiler expects that the runtime library contains certain subroutines. If you see this error and you didn’t change the runtime library code, it’s very likely that the runtime library you’re using doesn’t match the compiler in use. If you changed the runtime library this error means that you removed a subroutine which the compiler needs for internal use.
Fatal: Cannot find system type ”arg1”. Check if you use the correct run time library.
  The compiler expects that the runtime library contains certain type definitions. If you see this error and you didn’t change the runtime library code, it’s very likely that the runtime library you’re using doesn’t match the compiler in use. If you changed the runtime library this error means that you removed a type which the compiler needs for internal use.
Hint: Inherited call to abstract method ignored
  This message appears only in Delphi mode when you call an abstract method of a parent class via inherited;. The call is then ignored.
Error: Goto label ”arg1” not defined or optimized away
  The label used in the goto definition is not defined or optimized away by the unreachable code elemination.
Fatal: Cannot find type ”arg1” in unit ”arg2”. Check if you use the correct run time library.
  The compiler expects that the runtime library contains certain type definitions. If you see this error and you didn’t change the runtime library code, it’s very likely that the runtime library you’re using doesn’t match the compiler in use. If you changed the runtime library this error means that you removed a type which the compiler needs for internal use.
Error: Interprocedural gotos are allowed only to outer subroutines
  Gotos between subroutines are only allowed if the goto jumps from an inner to an outer subroutine or from a subroutine to the main program
Error: Label must be defined in the same scope as it is declared
  In ISO mode, labels must be defined in the same scope as they are declared.
Error: Leaving procedures containing explicit or implicit exceptions frames using goto is not allowed
  Non-local gotos might not be used to leave procedures using exceptions either implicitly or explicitly. Procedures which use automated types like ansistrings or class constructurs are affected by this too.

[next] [prev] [prev-tail] [front] [up]