From b47c302bbffd668334f307d512b674f804f8f2fc Mon Sep 17 00:00:00 2001 From: _ov4 Date: Sat, 17 Oct 2026 10:35:33 +0000 Subject: docs: document OVERLOAD Co-Authored-By: Claude Opus 5.5 --- doc/language/keyword/cpsc-keyword-include.7.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/language/keyword/cpsc-keyword-include.7.md') diff --git a/doc/language/keyword/cpsc-keyword-include.7.md b/doc/language/keyword/cpsc-keyword-include.7.md index 5600472..95ff953 100644 --- a/doc/language/keyword/cpsc-keyword-include.7.md +++ b/doc/language/keyword/cpsc-keyword-include.7.md @@ -14,7 +14,7 @@ INCLUDE "path.cps" INCLUDE is a compiler extension, allowed only at top level. Resolve the path relative to the including source's directory. The included file must also be given on the command line; symbolic and hard links identify the same file. -Import functions, procedures, types (including enum values), classes and methods, top-level constants and GLOBAL variables. Imports are transitive. Repeated includes and cycles are harmless: INCLUDE imports symbols rather than copying statements. A file always sees its own definitions. Using an unimported definition produces the usual unknown or undefined name error. Definitions must be unique across all input files, even when they are not imported. +Import functions, procedures, types (including enum values), classes and methods, top-level constants and GLOBAL variables. Imports are transitive. Repeated includes and cycles are harmless: INCLUDE imports symbols rather than copying statements. A file always sees its own definitions. Using an unimported definition produces the usual unknown or undefined name error. Definitions must be unique across all input files, even when they are not imported. Explicit OVERLOAD definitions may share a name across files when their parameter signatures differ; callers see only visible overloads. See [cpsc-keyword-overload(7)](cpsc-keyword-overload.7.md). Imported constants are visible from the start of the including unit. A unit's own constants retain their ordinary declaration-order visibility. Top-level DECLARE variables are entry-program locals and are not exported. Pass all inputs together; there is no separate object-file compilation mode. -- cgit v1.3.1-4-g156e