VSC suggestions

The following are my observations of issues with using VSC. Then my approach to dealing with the issue. Should you find other issues, please let me know and I will add to this list.

These are in no particular order

NULL is flagged as an error
The first use of NULL in every file is underscored with red squiggles to indicate an error. This seems to be a bug in VSC's reading of C header files.
Workarround: add the following to the top of every .c file
```
#ifndef NULL
#define NULL (void *) 0
#endif
                
```
This will satisfy VSC and not cause compilation problems.
When using SFTP, files renamed on my laptop are not renamed on the Unix servers.
This is weird, the files still get updated, but with their old names.
Workarround: do not use the "rename" function (ctrl-click on file in list an select rename). Instead, close the file (if you have an open editor), go to a terminal (powershell) window and rename the file that way (e.g., mv x y).
In the C/C++ configuration (F1 then serach for "C/C++: Edit Config.." set the value of "cStandard" to c11.This will avoid some things getting flagged as errors