From 92b1588202309bec9337b02ef47a682911c65fdd Mon Sep 17 00:00:00 2001 From: David Schmenk Date: Fri, 15 Dec 2017 13:31:05 -0800 Subject: [PATCH] Updated Home (markdown) --- Home.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Home.md b/Home.md index a23811c..5905242 100644 --- a/Home.md +++ b/Home.md @@ -6,7 +6,7 @@ The larger libraries provide an API based on function pointers. This allows mach ``` libAPI:someFunc() ``` -If the function doesn't have any parameters, the `()` are still required because the function will be accessed as just a `word` without them. The syntax superficially resembles object oriented language constructs and not by accident. Note that function pointers don't get the same parameter/return values checking that regular function definitions get. The libraries APIs all return one value from every function so there isn't a danger of forgetting to override the return value count. However, the parameter counts aren't verified so you need to beware of getting them correct. +If the function doesn't have any parameters, the `()` are still required because the function will be accessed as just a `word` without them. The syntax superficially resembles object oriented language constructs and not by accident. Note that function pointers don't get the same parameter/return values checking that regular function definitions get. All library APIs return one value from every function so there isn't a danger of forgetting to override the return value count. However, the parameter counts aren't verified so you need to beware of getting them correct. Smaller library APIs will export the individual functions and you will call them just like any other. ## PLASMA Sample Code: