Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
L LangOptum
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Nuclaer
  • LangOptum
  • Wiki
  • File Inclusion

Last edited by Nuclaer Apr 25, 2020
Page history

File Inclusion

import somepackage

import will scan the compilation path for .lo files matching the package name. When it finds it, it will add all class and function declarations. It does not have to compile those files. This allows the header files and source files to be the same files (unlike C, C++, etc). The compiler may walk the import tree compiling every file, or it may simply use declarations from the import tree, whichever is decided at compilation time.

Clone repository
  • Builtins
  • Compiler Mechanics
  • Compiler Structure
  • Desired Builtin Libraries
  • File Inclusion
  • Home
  • OOP
  • Operator Notes
  • Preprocessor
  • Program Control
  • Variable Types
  • language
  • lort (LO RunTime)