nsf

Clone Tools
  • last updated 11 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
improved spelling

Tcl9 fix: fixed handling of leading "~" in file paths.

In the Unix shell tradition, leading "~" in file paths denotes

to the home directory. In Tcl9, we have to use [file home] instead.

    • -1
    • +1
    /library/xotcl/library/comm/Httpd.xotcl
    • -1
    • +1
    /library/xotcl/library/comm/Mime.xotcl
New feature: Added method nx::Object->"info consts"

A "const" is a variable that cannot be altered later. So far, such

constant variables have to be created via the Tcl9 "const" cmd, like

in the example below. The introspection method "/obj/ info consts" is

very similar to "/obj/ info vars", but it lists only unmodifiable

variables.

nx::Object create o {

#

# Create a "const" instance variable

#

const :x 1

set :y 2

...

}

puts [o info consts]

puts [o info vars]

fixed typo (space was missing)

re-establish sanity check

minor cleanup of debug and log messages

Remove CI/CD support for the Tcl 8.5.19 release. See ticket #2

improved warning message, when Tcl command "::history" is not defined

updated year in comment

fixed false positive in memcount statistics

Before this fix, we saw messages like the following accompanied with wrong memcount

statistics, when running library/xotcl/tests/testo.xotcl

******** MEM COUNT ALERT: Trying to free 0x14f91fc10 <Tcl_Obj* *>, but was not allocated

regression test: increased independency of test cases

Add Announce2.4.1 and ChangeLog-2.4.0-HEAD drafts [skip ci]

    • -0
    • +311
    /ChangeLog-2.4.0-HEAD
Merge branch 'memleak-nsfparam-issue1' into 'main'

Memleak nsfparam issue1

See merge request tcltk/nsf!1

Memleak nsfparam issue1

added one more test to pinpoint issue #3 with Tcl 8.5.19

added casts to debug output

Make handling of colonLocalVarCache more type-safe

Since the usual macro TCL_SIZE_T does not work together with the

macros for the memcount macros, a new typedef "Nsf_Tcl_Size_t" was

introduced. Using a typedef is better and eases maintenance. The new

typedef has a "Nsf_" prefix, since it is defined in nsf.h.

fix for issue #4; Memory leak of NsfMethodContext with Tcl9

Ths is not a fully satisfying fix, since it just fixes the symptom, not the cause.

Also the old variant is supposed to run free of this issue. However, we are

talking here about a single Tcl_Obj inside the nx object system, so the harm

is very limited. More details in the ticket.

removed mostly obsolete hint

memcount: fix type spec leading to a wrong false positive on memcount tests

* nsf.c (ParamFreeInternalRep): Remove some left-over.

* nsf.c (NsfParamWrapper): refcount mini-reform removing canFree flag

Update build matrix: Use gcc-12 on macOS images [skip travis]

Update build matrix: 9.0.0 and 8.6.15

Improved Tcl 9.0.0 compatibility

One needs 'Tcl_InitStubs(interp, "8.5-",...)' instead of

'Tcl_InitStubs(interp, "8.5",...)', since the semantics are seemingly

the same as in "package require ...". Not sure, why we have not seen

this with earlier pre-releases of Tcl9.

Without this change, we see in the NaviServer regression test the following error message:

[27/Sep/2024:10:56:30][18309.7f35ed856540][-main:test-] Error: version conflict for package "tcl": have 9.0.0, need 8.5

: version conflict for package "tcl": have 9.0.0, need 8.5

: while executing

: "load {} Nsf"

: invoked from within

: "ns_ictl update"

: (procedure "ns_cleanup" line 8)

: invoked from within

Update build matrix to include the 9.0b3 release

* win/rules.vc: Tcl 9 does not add a version infix to the stub library name [skip actions]

Fix appveyor build descriptor [skip actions]

Merge branch 'main' of git.complex.wu.ac.at:tcltk/nsf

fix for transitional bug due to NS_TCL_HAVE_TIP629

Deactivating NS_TCL_HAVE_TIP629, since this needs more work to deal

with the two different types of commands (before and after the TIP)

* When we activate NS_TCL_HAVE_TIP629 (TIP supporting > 2^31

* elements in object vectors), Tcl defines different objProcs

* (Tcl_ObjCmdProc and Tcl_ObjCmdProc2) where the usage of these

* depends on a cmdWrapperProc. Unfortunately, the resolving of

* these are performed via CmdWrapperInfo, which is not exported. We

* have to think how to resolve these to make this working as with

* prior Tcl versions.