jimtcl | Official repository of Jim Tcl | Script Programming library

by msteveb C Version: 0.82 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | jimtcl Summary

jimtcl is a C library typically used in Programming Style, Script Programming applications. jimtcl has no bugs, it has no vulnerabilities and it has low support. However jimtcl has a Non-SPDX License. You can download it from GitHub.

Jim is a small footprint implementation of the Tcl programming language written from scratch. Currently Jim Tcl is very feature complete with an extensive test suite (see the tests directory). There are some Tcl commands and features which are not implemented (and likely never will be), including traces and Tk. However Jim Tcl offers a number of both Tcl8.5 and Tcl8.6 features ({*}, dict, lassign, tailcall and optional UTF-8 support) and some unique features. These unique features include [lambda] with garbage collection, a general GC/references system, arrays as syntax sugar for [dict]tionaries, object-based I/O and more. Other common features of the Tcl programming language are present, like the "everything is a string" behaviour, implemented internally as dual ported objects to ensure that the execution time does not reflect the semantic of the language :).

Support

Quality

Security

License

Reuse

Support

jimtcl has a low active ecosystem.

It has 382 star(s) with 102 fork(s). There are 24 watchers for this library.

It had no major release in the last 12 months.

There are 6 open issues and 121 have been closed. On average issues are closed in 153 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of jimtcl is 0.82

Quality

jimtcl has 0 bugs and 0 code smells.

Security

jimtcl has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jimtcl code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jimtcl has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

jimtcl releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of jimtcl

Get all kandi verified functions for this library.

jimtcl Key Features

No Key Features are available at this moment for jimtcl.

jimtcl Examples and Code Snippets

No Code Snippets are available at this moment for jimtcl.

Community Discussions

Trending Discussions on jimtcl

info vars command is not working properly inside a proc

QUESTION

info vars command is not working properly inside a proc

Asked 2021-Aug-19 at 07:26

I am tring to do some variable auto-completion using TCL (this is intended for jimtcl)

I have tried the following sequence in both tclsh and jimsh:

...

ANSWER

Answered 2021-Aug-18 at 22:28

This is a namespace problem.

A proc has its own namespace. When you're running info vars at the tclsh prompt, that's the global :: namespace.

The simplest thing to do in your proc would be to add :: to your argument to info vars

return [lsort [info vars ::$vars_pattern]]

The return values will include the :: namespace prefix, so remove that first if you need to.

Funny that you're seeing this problem with an auto-completion application. I've written a Tcl script to dump out all my procs, commands, namespaces, etc into json files that I read into Vim for a custom auto-completion plugin. I found the very same problems while writing that.

Source https://stackoverflow.com/questions/68839781

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jimtcl

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: