Update content for additional parameters (1.9.0)

Author: ypzhao-rocket

docs/index.md

@@ -62,7 +62,7 @@ Requirements: [VS Code](https://code.visualstudio.com/) 1.70.2 or higher version
 
 	**Note**: Using this method, an existing working environment that requires a different version of Java would not be impacted and the extension will work properly in the Java 11 (or above) environment.
 
-  3. Select "File" > "Open Folder" to pen a folder that contains the BASIC program files you want to view or edit. You can also add multiple folders to the workspace using "File" > "Add Folder to Workspace". We recommend that you open the U2 account level folders to avoid encountering exceptions.
+  3. Select "File" > "Open Folder" to open a folder that contains the BASIC program files you want to view or edit. You can also add multiple folders to the workspace using "File" > "Add Folder to Workspace". We recommend that you open the U2 account level folders to avoid encountering exceptions.
 
 	**Note**: This extension is designed to work with folders/directories rather than individual program files. If you open a single file, some functions may be limited.
 

docs/usage/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Change Log
 
+## Version 1.9.0: January 5, 2023
+
+ - Enhancement: support additional parameters for compilation
+ - Enhancement: support additional parameters for debugging
+
 ## Version 1.8.0: October 27, 2022
 
 - Feature: support logging system. Please refer online documentation for details.

docs/usage/Compile.md

@@ -63,7 +63,8 @@ A default build task configuration will be created and displayed in the editor.
 			"type": "BASIC",
 			"targets": [],
 			"compile": {
-				"dataSource": "UNIVERSE"
+				"dataSource": "UNIVERSE", 
+				"arguments": ""
 			},
 			"problemMatcher": [],
 			"label": "BASIC: Build", 
@@ -89,7 +90,7 @@ You can find task properties in the [VS Code official documents](https://code.vi
   - **language**: (For UniData only) The programming language flavor. Must be "UniBasic" or "Pick". If not set, "UniBasic" is the default.
   - **catalog**: For UniVerse, you can select "global", "local" or "normal". For UniData, you can select "global", "local" or "direct". If not set, files will not be cataloged.
   - **initialCharacter**: (For UniVerse only) The initial character of the cataloged program can only be set when the **catalog** parameter is set to “global”.
-
+  - **arguments**: Put additional compilation arguments here. For more details, please refer UniVerse / UniData user manual for more details. By default, this setting doesn’t appear in the configuration file. Please add it manually if needed.
 #### Run build task
 
 Select "Run build task" from the "Terminal" menu to start the build task.
@@ -99,7 +100,6 @@ Select "Run build task" from the "Terminal" menu to start the build task.
 ![](../img/compile_from_menu_3.png)
 
 
-
 ## UniVerse Compile Task Examples
 
 **Example 1**. Compile a single BASIC program without cataloging. 
@@ -361,3 +361,31 @@ Select "Run build task" from the "Terminal" menu to start the build task.
 
 - Add another task object in "tasks"
 - Change "label" in the tasks, When run build tasks, you can select one of these tasks
+
+**Example 4**. Additional compilation arguments
+
+```json
+{
+	"version": "2.0.0",
+	"tasks": [
+		{
+			"type": "BASIC",
+			"targets": [
+				"BP/SAMPLE_FILE"
+			],
+			"compile": {
+				"dataSource":"UNIVERSE", 
+				"arguments": "-L -X"
+			},
+			"problemMatcher": [],
+			"label": "BASIC: Build",
+			"group": {
+				"kind": "build",
+				"isDefault": true
+			}
+		}
+    ]
+}
+```
+
+- Compile the BASIC program with arguments "-L" and "-X".

docs/usage/Debugging.md

@@ -1,12 +1,12 @@
-## Debugging (Preview)
+## Debugging
 
-With the debugging function, user can easily debug BASIC programs, observe, track the results and changes to variables for each step when running a BASIC program. 
+With the debugging function, users can easily debug BASIC programs, as well as observe and track the results and changes to variables for each step when running a BASIC program. 
 
-The 1.7.0 version of the debugging function is a preview version. There are limitations to the debugging features and not all debugging functions are stable. The following U2 server versions and platforms are supported:
+The following U2 server versions and platforms are supported:
 
 ### UniVerse
 
-Versions: 12.1.1 and before
+Versions: 11.3.2 or higher
 
 Platforms: Windows, Linux, AIX
 
@@ -24,6 +24,8 @@ In the 1.6.0 release, additional binaries should be installed on UniVerse to sup
 
 ## Start Debugging
 
+**Note**: You should not debug BASIC subroutines direcly, because this not allowed in UniVerse and UniData.
+
 ### Connecting to a U2 server account folder
 
 Before using the debugging feature, you must connect to a U2 server account folder firstly. Please see the [Connection section](./Connection.md) to learn how to connect to a U2 server account.
@@ -36,6 +38,8 @@ There are 2 methods to debug a BASIC program file: debugging without a launch fi
 
 Before debugging, open the BASIC program first.
 
+**Note**: debugging a BASIC subroutine directly is not allowed
+
 ### Debugging without a launch file
 
  - Click the **Run and Debug** icon on left menu bar. The **Run and Debug** view will display if you have no `launch.json` file in your project.
@@ -71,7 +75,8 @@ Then a default debugging configuration file launch.json will be generated in dir
             "program": "",
             "stopOnEntry": true,
             "preLaunchTask": "BASIC: Build",
-            "dependencies": []
+            "dependencies": [], 
+            "arguments": ""
         }
     ]
 }
@@ -84,6 +89,7 @@ Then a default debugging configuration file launch.json will be generated in dir
  - "stopOnEntry": used to control whether the program will be stopped at the first runnable line when start debugging. Currently only true is supported.
  - "preLanuchTask": this is used to run pre-required task before debugging. In our extension, we use this setting to compile the BASIC program in setting "program" first.
  - "depenedncies": put other BASIC program files here if they need to be compiled before debugging.
+ - "arguments": put additional debugging arguments here. Please refer to your UniVerse / UniData user documentation for more details. By default, this setting doesn’t appear in the configuration file, but can be added manually if needed.
 
 From the **Run and Debug** view, set the launch option to **Launch Program**. Then press the F5 button to start debugging.