Ticket #303

Some of these (like missing getpeername) are reasonable, but
it seems like an odd platform that declares but doesn't implement
access and umask, and implements but doesn't declare lstat.

These changes need testing to see if enough works to be useful.

Signed-off-by: Steve Bennett <steveb@workware.net.au>

Signed-off-by: Steve Bennett <steveb@workware.net.au>

In the case there is nothing to insert

Could be provoked with: lreplace {a b} 0 0

Fixes: #300
Signed-off-by: Steve Bennett <steveb@workware.net.au>

Signed-off-by: Steve Bennett <steveb@workware.net.au>

Now that we rely on eval frames to unwind the stack on error,
if an error occurs at the top level it would previously not
provide a stack trace. e.g.

$ jimsh t.tcl
unmatched "["

After this change, the error location is now correctly reported:

$ ./jimsh t.tcl
t.tcl:8: Error: unmatched "["
Traceback (most recent call last):
  File "t.tcl", line 8

Signed-off-by: Steve Bennett <steveb@workware.net.au>

Now that the I/O subsystem does auto-flush on write we no longer
need to manually set up a writable handler.

If $ is followed by something that isn't a variable name,
previously all subsequent variables were being ignored.

Fixes #296

Signed-off-by: Steve Bennett <steveb@workware.net.au>

RTS, DTR, etc. and sending a break condition

Signed-off-by: Steve Bennett <steveb@workware.net.au>

xonxoff start and stop chars

Signed-off-by: Steve Bennett <steveb@workware.net.au>

To avoid linking with -lutil if possible

Signed-off-by: Steve Bennett <steveb@workware.net.au>

And explain in the manual that it isn't allowed.

Fixes: #285

Signed-off-by: Steve Bennett <steveb@workware.net.au>

Where a NULL script is pushed on the stack

Fixes #290

Signed-off-by: Steve Bennett <steveb@workware.net.au>

Per Tcl 8.7

Signed-off-by: Steve Bennett <steveb@workware.net.au>

Add CodeQL Workflow for Code Security Analysis

This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats.

We added a new CodeQL workflow file (.github/workflows/codeql.yml) that
- Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience).
- Runs daily.
- Excludes queries with a high false positive rate or low-severity findings.
- Does not display results for git submodules, focusing only on our own codebase.

Testing:
To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code.

Deployment:
Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps:
1. Under the repository name, click on the Security tab.
2. In the left sidebar, click Code scanning alerts.

Additional Information:
- You can further customize the workflow to adapt to your specific needs by modifying the workflow file.
- For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/

).

Signed-off-by: Brian <bayuan@purdue.edu>

Add CodeQL Workflow for Code Security Analysis

This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats.

We added a new CodeQL workflow file (.github/workflows/codeql.yml) that
- Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience).
- Runs daily.
- Excludes queries with a high false positive rate or low-severity findings.
- Does not display results for git submodules, focusing only on our own codebase.

Testing:
To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code.

Deployment:
Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps:
1. Under the repository name, click on the Security tab.
2. In the left sidebar, click Code scanning alerts.

Additional Information:
- You can further customize the workflow to adapt to your specific needs by modifying the workflow file.
- For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/

).

Signed-off-by: Brian <bayuan@purdue.edu>

Add CodeQL Workflow for Code Security Analysis

This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats.

We added a new CodeQL workflow file (.github/workflows/codeql.yml) that
- Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience).
- Runs daily.
- Excludes queries with a high false positive rate or low-severity findings.
- Does not display results for git submodules, focusing only on our own codebase.

Testing:
To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code.

Deployment:
Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps:
1. Under the repository name, click on the Security tab.
2. In the left sidebar, click Code scanning alerts.

Additional Information:
- You can further customize the workflow to adapt to your specific needs by modifying the workflow file.
- For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/

).

Signed-off-by: Brian <bayuan@purdue.edu>

Add CodeQL Workflow for Code Security Analysis

This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats.

We added a new CodeQL workflow file (.github/workflows/codeql.yml) that
- Runs on every push and pull request to the main branch.
- Excludes queries with a high false positive rate or low-severity findings.
- Does not display results for third-party code, focusing only on our own codebase.

Testing:
To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code.

Deployment:
Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps:
1. Under the repository name, click on the Security tab.
2. In the left sidebar, click Code scanning alerts.

Additional Information:
- You can further customize the workflow to adapt to your specific needs by modifying the workflow file.
- For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation.

Signed-off-by: Brian <bayuan@purdue.edu>

On systems where we aren't getting enough cpu time.
Heuristic check, but probably good enough in practice.

Fixes #282

Signed-off-by: Steve Bennett <steveb@workware.net.au>

This bug has been there for a long time but probably no-one builds
static extensions because they aren't very useful.

Signed-off-by: Steve Bennett <steveb@workware.net.au>

- Set jim::lineedit to indicate if line editing is configured
- Ensure that aio tty works even if line editing is disabled
- Skip some tests if line editing is not configured

Signed-off-by: Steve Bennett <steveb@workware.net.au>

To show that it returns the current values, not just the original values

Signed-off-by: Steve Bennett <steveb@workware.net.au>

hurd does not return the path for unix domain sockets
via getsockname()

Signed-off-by: Steve Bennett <steveb@workware.net.au>

socket operation on non-socket gives a different message

Signed-off-by: Steve Bennett <steveb@workware.net.au>

Signed-off-by: Steve Bennett <steveb@workware.net.au>

When the multi-level break/continue support was added in
1b151f81

 it reused returnLevel,
but this interferred with the return level returned by try/catch.
Use a separate variable for the break/continue level.

Signed-off-by: Steve Bennett <steveb@workware.net.au>

And allow -DJIM_TINY to disable optimisation, and
use that with bootstrap jimsh.

Fixes #273

Signed-off-by: Steve Bennett <steveb@workware.net.au>

Need strings.h for strcasecmp

(Although I don't really think it's necessary to support lower case
versions of signal names. This will probably change).

Fixes #270

Signed-off-by: Steve Bennett <steveb@workware.net.au>

If pkg-config is not available

Fixes #272

Signed-off-by: Steve Bennett <steveb@workware.net.au>

This test can be at bit flaky on slower machines
(perhaps running under a VM or qemu).

Signed-off-by: Steve Bennett <steveb@workware.net.au>

Mostly for update bootstrap jimsh

Signed-off-by: Steve Bennett <steveb@workware.net.au>

Without this, readdir() doesn't work properly on some 32 bit platforms

Signed-off-by: Steve Bennett <steveb@workware.net.au>

And allow current source file to be set

Fixes: #268

Signed-off-by: Steve Bennett <steveb@workware.net.au>

The checks for -ipv6, -async broke 'socket -commands'

Signed-off-by: Steve Bennett <steveb@workware.net.au>

In case socket pty, interp are not available

Signed-off-by: Steve Bennett <steveb@workware.net.au>

set a 5

proc b {} {&a} {
	incr a
}

b

Now a is 6 because b captured a by reference instead of by value

Signed-off-by: Steve Bennett <steveb@workware.net.au>