Difference between revisions of "MC-Basic:OLOAD$"
(7 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
+ | {{Languages|MC-Basic:OLOAD$}} | ||
{{MC-Basic | {{MC-Basic | ||
|SHORT FORM= | |SHORT FORM= | ||
Line 7: | Line 8: | ||
|AVAILABILITY= | |AVAILABILITY= | ||
− | Version 4.5.3 | + | Since Version 4.5.3 |
|DESCRIPTION= | |DESCRIPTION= | ||
Line 40: | Line 41: | ||
|SEE ALSO= | |SEE ALSO= | ||
− | * [[ | + | * [[MC-Basic:OLOAD|OLOAD]] |
− | * [[ | + | * [[MC-Basic:OUNLOAD|OUNLOAD]] |
− | * [[ | + | * [[MC-Basic:OUNLOAD$|OUNLOAD$]] |
− | |||
+ | [[Category:MC-Basic:C-Interface|OLOAD$]] | ||
}} | }} |
Latest revision as of 02:13, 25 April 2017
Language: | English • 中文(简体) |
---|
Loads object module into the system’s memory. The object file must be compiled by a GNU C compiler. When OLOAD$ command fails, a diagnostic file named OLOAD.ERR containing the loading errors is created. The OLOAD.ERR can be retrieved.
Syntax
OLOAD$ <object file name string>
Availability
Since Version 4.5.3
Type
<object file name string>: string
Scope
Task , Config , Terminal
Examples
OLoad$ “myObj.o”
Common shared ObjName as string = “myObj.o”
OLoad$ ObjName