This prevents situations where the delproc function (e.g. for aio) access already deleted singleton objects.

Fixes #312

Signed-off-by: Steve Bennett <steveb@workware.net.au> Leaf check-in: 90458343f7 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 46c97b7bee user: steveb@workware.net.au tags: trunk,

$handle buffering full <writelimit> $handle readsize <size>

These now return the current buffering and read size respectively

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: f5562e68e0 user: steveb@workware.net.au tags: trunk,

Ability to increase read buffer size. Ability to increase write buffering limit in full mode.

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 76aaf41f57 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 8f06362103 user: steveb@workware.net.au tags: trunk,

Use after instead because otherwise the alarm in the readable script which confuses things later.

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: d4716f0369 user: steveb@workware.net.au tags: trunk,

Expect output to stderr when an error happens inside bgerror, so catch it.

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 5e46141844 user: steveb@workware.net.au tags: trunk,

When running under tclsh

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 0d6dc571fe user: steveb@workware.net.au tags: trunk,

Unknown commands are automatically passed through to the underlying handle

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: d8d03a2c9d user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 571abde016 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: bf798ba594 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: fffe5481e2 user: steveb@workware.net.au tags: trunk,

If SIGPIPE is blocked, write may return EPIPE. On interpreter shutdown we try to flush write buffers and in this case we are likely to get an unexpected SIGPIPE since the signal may no longer be blocked.

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 7b3a1076c4 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 9e42109d78 user: steveb@workware.net.au tags: trunk,

Some versions don't included needed stdio.h

Fixes: #308

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: fb416a0204 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> Leaf check-in: aef743c7f7 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: ebddaf7688 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 999ee0336a user: steveb@workware.net.au tags: trunk,

To avoid invalid JSON causing core dumps.

Minor changes to the jsmn parser to still allow Infinity and NaN.

Fix some tests that didn't use strictly correct JSON.

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 3ed5c18abe user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 93a9711068 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 4dad7a5106 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 3c6e52d942 user: steveb@workware.net.au tags: trunk,

Update shipped docs

Signed-off-by: Steve Bennett <steveb@workware.net.au> Leaf check-in: 4226be27f1 user: steveb@workware.net.au tags: trunk

And remove DEVELOPING as it is out-of-date

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 78fd9dcd71 user: steveb@workware.net.au tags: trunk,

Need to delete the commands hash table before calling Jim_InterpIncrProcEpoch() as otherwise the commands won't yet be in the "old command" list to be deleted.

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 80dd2df641 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: dcd6e67cc5 user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: b2d537df2d user: steveb@workware.net.au tags: trunk,

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> check-in: 5f7ce8c3cf user: steveb@workware.net.au tags: trunk,

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 59884b7ed4 user: steveb@workware.net.au tags: trunk,

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> check-in: deaf366831 user: steveb@workware.net.au tags: trunk,

Now that the I/O subsystem does auto-flush on write we no longer need to manually set up a writable handler. check-in: 2cad2323c2 user: steveb@workware.net.au tags: trunk,

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> check-in: 94b1e0ee45 user: steveb@workware.net.au tags: trunk,

RTS, DTR, etc. and sending a break condition

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: db4667df2f user: steveb@workware.net.au tags: trunk,

xonxoff start and stop chars

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 3c914456bb user: steveb@workware.net.au tags: trunk,

To avoid linking with -lutil if possible

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 019d916486 user: steveb@workware.net.au tags: trunk,

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

Fixes: #285

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 745a697450 user: steveb@workware.net.au tags: trunk,

Where a NULL script is pushed on the stack

Fixes #290

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 2a298c808a user: steveb@workware.net.au tags: trunk,

Per Tcl 8.7

Signed-off-by: Steve Bennett <steveb@workware.net.au> check-in: 5742b905cb user: steveb@workware.net.au tags: trunk,

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> check-in: 180bbfc60f user: steveb@workware.net.au tags: trunk,

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> check-in: e6f589be32 user: steveb@workware.net.au tags: trunk,

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> check-in: 5ddd549e38 user: steveb@workware.net.au tags: trunk,

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> check-in: 3493fd7b5f user: steveb@workware.net.au tags: trunk,

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> check-in: 534c93399f user: steveb@workware.net.au tags: trunk,