tcl-core — Tcl Core Team discussions about Tcl development

[TCLCORE] March 11 2025 Tcl monthly meetup reminder

[Steve L. <st...@di...>]

A reminder that the next meetup will be held Tuesday March 11 2025 at [clock format 1741683600]  Tuesday 2am US West, 4am US Central, 5am US East, 9am UTC, 9am UK, 10am Western Europe, 2:30pm India, 5pm Australia West / Singapore / China, 6pm Japan, 8pm Australia East, 10pm New Zealand.

Details (including how to connect) are available via
https://wiki.tcl-lang.org/page/Monthly+Virtual+Meetup

-- Steve

Re: [TCLCORE] MS-Win: remove XP dialogs?

[Harald O. <har...@el...>]

After those positive feed-backs, I have authered a ticket:

https://core.tcl-lang.org/tk/tktview/441c526c0db25bf40389b74b7e7821f13efe472f

The ticket states, that this is changed without a TIP.
It also states, that this is for Tk9.1 only and will not be back-ported.

I invite anybody to speek-up at the ticket, if this is not ok.

Thanks for all,
Harald

Am 10.03.2025 um 10:12 schrieb Harald Oehlmann:
> Am 09.03.2025 um 18:03 schrieb apn...@ya...:
>> +1. Probably could have been done for 9.0 but better late than never.
>>
>> Will use of the option be ignored or raise an error?
> 
> Thanks for the answer.
> As it was never documented, I would raise an error as the cleaner version.
> 
> Thanks,
> Harald
> 
> 
>>
>> Yahoo Mail: Search, organise, conquer <https:// 
>> mail.onelink.me/107872968? 
>> pid=nativeplacement&c=US_Acquisition_YMktg_315_SearchOrgConquer_EmailSignature&af_sub1=Acquisition&af_sub2=US_YMktg&af_sub3=&af_sub4=100002039&af_sub5=C01_Email_Static_&af_ios_store_cpp=0c38e4b0-a27e-40f9-a211-f4e2de32ab91&af_android_url=https://play.google.com/store/apps/details?id=com.yahoo.mobile.client.android.mail&listing=search_organize_conquer>
>>
>>     On Sun, 9 Mar 2025 at 7:32 pm, Jan Nijtmans
>>     <jan...@gm...> wrote:
>>     Op di 4 mrt 2025, 19:48 schreef Harald Oehlmann:
>>
>>         Is it an idea to remove those for 9.1 ?
>>
>>
>>     Yes, +1
>>
>>     Regards,
>>             Jan Nijtmans
>>

Re: [TCLCORE] MS-Win: remove XP dialogs?

[Harald O. <har...@el...>]

Am 09.03.2025 um 18:03 schrieb apn...@ya...:
> +1. Probably could have been done for 9.0 but better late than never.
> 
> Will use of the option be ignored or raise an error?

Thanks for the answer.
As it was never documented, I would raise an error as the cleaner version.

Thanks,
Harald


> 
> Yahoo Mail: Search, organise, conquer <https:// 
> mail.onelink.me/107872968? 
> pid=nativeplacement&c=US_Acquisition_YMktg_315_SearchOrgConquer_EmailSignature&af_sub1=Acquisition&af_sub2=US_YMktg&af_sub3=&af_sub4=100002039&af_sub5=C01_Email_Static_&af_ios_store_cpp=0c38e4b0-a27e-40f9-a211-f4e2de32ab91&af_android_url=https://play.google.com/store/apps/details?id=com.yahoo.mobile.client.android.mail&listing=search_organize_conquer>
> 
>     On Sun, 9 Mar 2025 at 7:32 pm, Jan Nijtmans
>     <jan...@gm...> wrote:
>     Op di 4 mrt 2025, 19:48 schreef Harald Oehlmann:
> 
>         Is it an idea to remove those for 9.1 ?
> 
> 
>     Yes, +1
> 
>     Regards,
>             Jan Nijtmans
> 

[TCLCORE] What platforms do we support?

[Francois V. <fvo...@fr...>]

Hi all,

I tried to find a list of platforms we TCT officially support for Tcl/Tk 
development, but I couldn't find anything else than:

https://www.tcl-lang.org/software/tcltk/platforms.html

which I'm questioning the up-to-date status (this is an euphemism).

Where can I read about, say:

- the macOS versions range we officially support (aqua builds)

- the fact we support macOS builds with XQuartz (or also other X servers)

- the range of Windows versions we support

- the list of Linux distros we support (perhaps)

- the fact that we don't support IRIX (any more), contrary to the above link

- and so on.

Something exhaustive, you see?

And then, what is the process for deprecating support for some platform? 
I guess a TIP is needed but IMO this would be logical only if there is 
an official list of supported platforms.

I'm asking because during a discussion I had yesterday with Marc Culler, 
the question about whether it is still useful or not to support macOS 
builds with XQuartz came up. We were questioning whether this was of any 
use to anyone. The list of supported platforms would have been one 
answer to the question (but yes, not THE answer).

Thanks,

François

[TCLCORE] [ANNOUNCE] ooxml (Excel im-/export) v1.10 Tcl9 ready

[Alexander S. <a.s...@gm...>]

ooxml ECMA-376 Office Open XML File Formats

since 1.7 ooxml is Tcl9 ready


SYSNOPSIS

   Read and Write Office Open XML "XLSX" since Excel 2007

   This package contains several commands to edit Excel files. The three most important
   are the following three:

       Importing Excel files into a Tcl array with ::ooxml::xl_read,
       export Tcl data to an Excel file with ::ooxml::xl_write and
       export Tcl tablelist to an Excel file with ::ooxml::tablelist_to_xl.

   For information on how to use these commands, see the examples and the man-page
   at https://fossil.sowaswie.de/ooxml.


API extract of command list
   …
   ::ooxml::xl_sheets file
   ::ooxml::xl_read file args
   ::ooxml::xl_write args
                    method numberformat args
                    method defaultdatestyle STYLEID
                    method font args
                    method fill args
                    method border args
                    method style args
                    method worksheet name
                    method column sheet args
                    method row sheet args
                    method cell sheet {data {}} args
                    method autofilter sheet indexFrom indexTo
                    method freeze sheet index
                    method printarea sheet indexFrom indexTo
                    method method merge sheet indexFrom indexTo
                    method presetstyles
                    method presetsheets
                    method method view args
                    method processPageMarigns defaults options
                    method pageMargins sheet args
                    method pageSetup sheet args
                    method write filename
   ::ooxml::tablelist_to_xl lb args
   …

DOWNLOAD

   https://fossil.sowaswie.de/ooxml/uv/download.html


DEPENDENCIES

   Tcl >= 8.6.7
   for reading: tcllib module zipfile::decode or tclvfs module vfs::zip >= 1.4.2 (recommended, zipfs is used from Tcl 9)
   tdom >= 0.9.0


GETTING THE CODE

   The development repository is hosted at https://fossil.sowaswie.de/ooxml
   You are encouraged to use trunk.


INSTALLING

   Simply extract the download ooxml-<version>.zip into your Tcl library path.

   Since ooxml is TEA-compatible you should be able to do

       ../configure
       make test
       make install


REPORTING BUGS

   Please head to https://fossil.sowaswie.de/ooxml/ticket and
   click on "New Ticket". Log in as anonymous and report your findings.
   If you prefer to have an individual login write Alex a mail.

Re: [TCLCORE] MS-Win: remove XP dialogs?

[<apn...@ya...>]

+1. Probably could have been done for 9.0 but better late than never. 
Will use of the option be ignored or raise an error? 

Yahoo Mail: Search, organise, conquer 
 
  On Sun, 9 Mar 2025 at 7:32 pm, Jan Nijtmans<jan...@gm...> wrote:   Op di 4 mrt 2025, 19:48 schreef Harald Oehlmann:
Is it an idea to remove those for 9.1 ?


Yes, +1
Regards,       Jan Nijtmans

_______________________________________________
Tcl-Core mailing list
Tcl...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-core
  

Re: [TCLCORE] MS-Win: remove XP dialogs?

[Jan N. <jan...@gm...>]

Op di 4 mrt 2025, 19:48 schreef Harald Oehlmann:

> Is it an idea to remove those for 9.1 ?
>

Yes, +1

Regards,
       Jan Nijtmans

>

[TCLCORE] Next bi-weekly conference in 3 weeks on 24th of March at 12:00 UTC

[Harald O. <har...@el...>]

Dear Tcl/Tk team,
the next bi-weekly Tcl/Tk telco will take place in 3 weeks:
24th of March 2025 at 12:00UTC on https://meet.jit.si/TclMonthlyMeetup

The meeting next Monday will be skipped in favour to the Monthly meetup 
on Tuesday.
The monthly meetup will take place:
11th of March at 9:00 UTC on https://meet.jit.si/TclMonthlyMeetup
https://wiki.tcl-lang.org/page/Monthly+Virtual+Meetup

Thank you all,
Harald

P.S.: I am not available next Tuesday for the meetup, sorry.

Re: [TCLCORE] DB2 failures with Tcl 9

[Steve S. <ste...@ha...>]

Ashok,

Many thanks again for your help with this, it proved a difficult issue 
to troubleshoot. So, as you say the db2tcl interface worked correctly 
with Tcl 8.6 on Linux and Windows and the ported version on Tcl 9.0 
worked with Linux, however on Windows 11 all of the Db2 CLI commands, 
such as follows would fail silently, without diagnostics.

     conn->rc = SQLAllocHandle (SQL_HANDLE_ENV, SQL_NULL_HANDLE, &henv);

I also wrote a test standalone program outside of Tcl with the same 
commands and compiler (VS2022) and this worked correctly, however moving 
these commands back into Tcl then failed. I spent many hours on this 
issue until your suggestion of removing the encoding line from the Tcl & 
TK manifest files resolved it.

It looks like an alternative could be to ask users to set DB2CODEPAGE 
(although the application has 500k+ downloads) however this is what it 
says in the IBM manual for users not to do this.

"Do not set DB2CODEPAGE unless explicitly stated in DB2 documentation, 
or directed to by IBM DB2 service personnel. Setting DB2CODEPAGE 
otherwise may produce unexpected results. Normally, setting DB2CODEPAGE 
is not required because DB2 derives the code page information from the 
operating system, and converts the data between the application and 
database code pages automatically."

Therefore going forward with a modified Tcl manifest file looks like the 
best solution for me.

Thanks again,

Steve

[TCLCORE] MS-Win: remove XP dialogs?

[Harald O. <har...@el...>]

Dear Tk group,
on the WIndows platform, there are still the XP style dialogs.
Those may be seen by the undocumented option "-xpstyle 1".

Try those:
tk_chooseDirectory -xpstyle 0
tk_chooseDirectory -xpstyle 1
tk_getOpenFile -xpstyle 1
tk_getOpenFile -xpstyle 0

Is it an idea to remove those for 9.1 ?

Thanks for all,
Harald

Re: [TCLCORE] Looking for someone to take over the @TclLang X feed

[Torsten B. <be...@ty...>]

OK, thanks. I do not use IFTTT, I settled for fedica (for now).

Regards, Torsten


> Am 04.03.2025 um 12:42 schrieb <apn...@ya...> <apn...@ya...>:
> 
> Great, thanks Torsten. I’ll contact you privately to hand over.
>  
> Not sure if relevant, but if you are referring to the IFTTT tool for posting to both, @dbohdan mentioned on the chat that it is now a paid service. FYI so you might need something else.
>  
> /Ashok
>  
> From: Torsten Berg <be...@ty...> 
> Sent: Tuesday, March 4, 2025 4:53 PM
> To: apn...@ya...
> Cc: tcl...@li...
> Subject: Re: [TCLCORE] Looking for someone to take over the @TclLang X feed
>  
> Hi,
>  
> As the one having started the account on Mastodon, I am probably the one to take over. I am willing to do that.
>  
> Steve had sent me the link to a tool which would enable me to post the content on Mastodon and X at the same time without the need to do it manually. I have been testing this tool for some time now and can say it works. It is still a bit laborious when you start interacting with users though, answering to user feedback. 
>  
> Having said this, however, I personally do not like X (anymore) for several reasons and have abandoned using it for myself. One problem is the length of the posts. On Mastodon, I have 500 characters which is enough to actually tell something that is more than a slogan. On X, I only have 280 which is very limited. I will not invest money to upgrade the account to a larger character count. So, we need to see how the tool handles long posts.
>  
> I would also like to encourage people on X to move over to Mastodon for a better user experience. If we find out that people are leaving X in substantial amounts, we may still be shutting the X account down in future.
>  
> Regards, Torsten
>  
>  
> 
> 
>> Am 04.03.2025 um 11:36 schrieb apnmbx-public--- via Tcl-Core <tcl...@li... <mailto:tcl...@li...>>:
>>  
>> I’ve been maintaining the X @TclLang feed for a few years. Now that the Fosstodon feed https://fosstodon.org/@tcl_tk is active (with better content to boot), I don’t plan on maintaining the X feed.
>>  
>> If anyone wants to take it over, let me know. Steve L mentioned mirroring from fosstodon or a common feed to both. That is another alternative if anyone is interested in tackling it.
>>  
>> Else I’ll shut it down in a couple of weeks.
>>  
>> /Ashok
>> _______________________________________________
>> Tcl-Core mailing list
>> Tcl...@li... <mailto:Tcl...@li...>
>> https://lists.sourceforge.net/lists/listinfo/tcl-core

Re: [TCLCORE] Looking for someone to take over the @TclLang X feed

[<apn...@ya...>]

Great, thanks Torsten. I’ll contact you privately to hand over.

 

Not sure if relevant, but if you are referring to the IFTTT tool for posting to both, @dbohdan mentioned on the chat that it is now a paid service. FYI so you might need something else.

 

/Ashok

 

From: Torsten Berg <be...@ty...> 
Sent: Tuesday, March 4, 2025 4:53 PM
To: apn...@ya...
Cc: tcl...@li...
Subject: Re: [TCLCORE] Looking for someone to take over the @TclLang X feed

 

Hi,

 

As the one having started the account on Mastodon, I am probably the one to take over. I am willing to do that.

 

Steve had sent me the link to a tool which would enable me to post the content on Mastodon and X at the same time without the need to do it manually. I have been testing this tool for some time now and can say it works. It is still a bit laborious when you start interacting with users though, answering to user feedback. 

 

Having said this, however, I personally do not like X (anymore) for several reasons and have abandoned using it for myself. One problem is the length of the posts. On Mastodon, I have 500 characters which is enough to actually tell something that is more than a slogan. On X, I only have 280 which is very limited. I will not invest money to upgrade the account to a larger character count. So, we need to see how the tool handles long posts.

 

I would also like to encourage people on X to move over to Mastodon for a better user experience. If we find out that people are leaving X in substantial amounts, we may still be shutting the X account down in future.

 

Regards, Torsten

 

 





Am 04.03.2025 um 11:36 schrieb apnmbx-public--- via Tcl-Core <tcl...@li... <mailto:tcl...@li...> >:

 

I’ve been maintaining the X @TclLang feed for a few years. Now that the Fosstodon feed  <https://fosstodon.org/@tcl_tk> https://fosstodon.org/@tcl_tk is active (with better content to boot), I don’t plan on maintaining the X feed.

 

If anyone wants to take it over, let me know. Steve L mentioned mirroring from fosstodon or a common feed to both. That is another alternative if anyone is interested in tackling it.

 

Else I’ll shut it down in a couple of weeks.

 

/Ashok

_______________________________________________
Tcl-Core mailing list
 <mailto:Tcl...@li...> Tcl...@li...
 <https://lists.sourceforge.net/lists/listinfo/tcl-core> https://lists.sourceforge.net/lists/listinfo/tcl-core

 

Re: [TCLCORE] Looking for someone to take over the @TclLang X feed

[Torsten B. <be...@ty...>]

Hi,

As the one having started the account on Mastodon, I am probably the one to take over. I am willing to do that.

Steve had sent me the link to a tool which would enable me to post the content on Mastodon and X at the same time without the need to do it manually. I have been testing this tool for some time now and can say it works. It is still a bit laborious when you start interacting with users though, answering to user feedback. 

Having said this, however, I personally do not like X (anymore) for several reasons and have abandoned using it for myself. One problem is the length of the posts. On Mastodon, I have 500 characters which is enough to actually tell something that is more than a slogan. On X, I only have 280 which is very limited. I will not invest money to upgrade the account to a larger character count. So, we need to see how the tool handles long posts.

I would also like to encourage people on X to move over to Mastodon for a better user experience. If we find out that people are leaving X in substantial amounts, we may still be shutting the X account down in future.

Regards, Torsten



> Am 04.03.2025 um 11:36 schrieb apnmbx-public--- via Tcl-Core <tcl...@li...>:
> 
> I’ve been maintaining the X @TclLang feed for a few years. Now that the Fosstodon feed https://fosstodon.org/@tcl_tk is active (with better content to boot), I don’t plan on maintaining the X feed.
>  
> If anyone wants to take it over, let me know. Steve L mentioned mirroring from fosstodon or a common feed to both. That is another alternative if anyone is interested in tackling it.
>  
> Else I’ll shut it down in a couple of weeks.
>  
> /Ashok
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li... <mailto:Tcl...@li...>
> https://lists.sourceforge.net/lists/listinfo/tcl-core

[TCLCORE] Looking for someone to take over the @TclLang X feed

[<apn...@ya...>]

I've been maintaining the X @TclLang feed for a few years. Now that the
Fosstodon feed https://fosstodon.org/@tcl_tk is active (with better content
to boot), I don't plan on maintaining the X feed.

 

If anyone wants to take it over, let me know. Steve L mentioned mirroring
from fosstodon or a common feed to both. That is another alternative if
anyone is interested in tackling it.

 

Else I'll shut it down in a couple of weeks.

 

/Ashok

Re: [TCLCORE] [External] Tcl + Thread on macOS Sequoia: fatal fork() error

[Gustaf N. (sslmail) <ne...@wu...>]

Is there a bug report for this? Where exactly does this happen? “Thread” means probably “built with —enable-threads”. 
It is well known and documented that fork() does not work well with threads. This affects all programs and is not related to tcl.
In certain situations, vfork() can be used instead.

-g

> On 28.02.2025, at 16:36, da Silva, Peter J <pet...@fl...> wrote:
> 
> I brought this up on our work slack and it’s apparently been a thing since 2005. Lots of CoreFoundation is non-reentrant or and gets all higgledy-piggledy if you fork() without exec()ing.
>  
> https://developer.apple.com/library/archive/technotes/tn2083/_index.html#//apple_ref/doc/uid/DTS10003794-CH1-SUBSECTION64
>  
> From: Donald G Porter via Tcl-Core <tcl...@li... <mailto:tcl...@li...>>
> Date: Friday, February 28, 2025 at 07:44
> To: Tcl List Core <tcl...@li... <mailto:tcl...@li...>>
> Subject: [External] [TCLCORE] Tcl + Thread on macOS Sequoia: fatal fork() error
> 
> 
> I've received a report that some of our programs running on macOS
> Sequoia 15.3.1 that are built on Tcl and Thread are failing with this
> error:
> 
>     The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
>     Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
> 
> Report is this problem occurs with both Tcl 8.6.16 and Tcl 9.0.0.
> 
> Before I start trying to chase it, is this a known problem and are there known remedies?
> 
> -- 
> | Don Porter            Applied and Computational Mathematics Division |
> | don...@ni... <mailto:don...@ni...>             Information Technology Laboratory |
> | https://urldefense.com/v3/__http://math.nist.gov/*DPorter/__;fg!!MvWE!DoYL8v6qzic5MoC0p4aMJs0RTzP8DqLadKpKLR0xsei2VDExC5ywTdKVO8t5_BDzqH52HLLx0H6K7ZL2xgJW7qnFyfMmXT0ATw$ <https://urldefense.com/v3/__http:/math.nist.gov/*DPorter/__;fg!!MvWE!DoYL8v6qzic5MoC0p4aMJs0RTzP8DqLadKpKLR0xsei2VDExC5ywTdKVO8t5_BDzqH52HLLx0H6K7ZL2xgJW7qnFyfMmXT0ATw$>                                   NIST |
> |______________________________________________________________________|
> 

Re: [TCLCORE] Tclx

[Brian G. <bri...@ea...>]

Thanks Paul. I found that repo and have started making the necessary changes. We'll see how it goes.

If anyone else has already done this, or is in process, do let me know!

Thanks!
-Brian

> On Feb 28, 2025, at 12:57, Paul Obermeier <pa...@po...> wrote:
> 
> Hi Brian,
> 
> I marked TclX in my BAWT framework as not Tcl9 capable.
> The latest version 8.6.3 available at https://github.com/flightaware/tclx/ does not work with Tcl9.
> 
> Paul
> 
> Am 28.02.2025 um 19:35 schrieb Brian Griffin:
>> Has anyone ported Tclx to 9?
>> 
>> -Brian
>> 
>> 
>> _______________________________________________
>> Tcl-Core mailing list
>> Tcl...@li...
>> https://lists.sourceforge.net/lists/listinfo/tcl-core
> 
> 
> 
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core
> 

Re: [TCLCORE] Tclx

[Paul O. <pa...@po...>]

Hi Brian,

I marked TclX in my BAWT framework as not Tcl9 capable.
The latest version 8.6.3 available at https://github.com/flightaware/tclx/ does not work with Tcl9.

Paul

Am 28.02.2025 um 19:35 schrieb Brian Griffin:
> Has anyone ported Tclx to 9?
>
> -Brian
>
>
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core

[TCLCORE] Tclx

[Brian G. <bri...@ea...>]

Has anyone ported Tclx to 9?

-Brian

[TCLCORE] Re. DB2 failures with Tcl 9

[<apn...@ya...>]

Steve,

 

[

CC'ing tcl-core re. DB2 driver failures with Tcl 9

 

(a) in case anyone can suggest alternative fixes or workarounds for Tcl 9 than what I suggested below, and 

 

(b) as background for a possible TIP  (See https://sourceforge.net/p/tcl/mailman/tcl-core/thread/005401dacea6%24011bc0e0%24035342a0%24%40yahoo.com/#msg58791944 for the context).

]

 

Glad to know the TPC DB2 drivers work after rebuilding tclsh without the manifest setting.

 

Just to close on the issue ...

 

The root cause of the failure you are seeing accessing IBM DB2 from Tcl 9 is that tclsh9 binds a manifest that forces the code page returned by the GetACP() call to UTF-8 regardless of the user and system setting. All DLL’s linked with tclsh will also be affected, including the DB2 driver.

 

As to why the DB2 driver fails as a result, I cannot say but I would guess that like much Windows software it may not by default handle MBCS encodings that exceed 2 bytes per character. Or maybe it does not like a mismatch between the application (tclsh) and database server code page setting. Don't really know.

 

Changing Tcl [encoding system] will not help as the DB2 driver is oblivious to it.

 

The reason this is not a problem with 8.6 is that Tcl 8 followed system settings for the code page.

 

The reason this is not a problem on other platforms or older Windows 10 releases is because Tcl 9 only forces UTF-8 after a certain Windows build number.

 

The reason (I am guessing this) SQL Server works is because they use the wide char API's and do not care about the code page setting.

 

Note rebuilding your own tclsh with the activeCodePage setting in the manifest stripped fixes the problem but has the issue that it will not read non-ASCII files written by "stock" tclsh without explicit use of -encoding. And vice versa. If you want to avoid rebuilding tclsh, your other *possible* solutions are: (I have not actually tried them, just guesses, so they may or may not work!)

 

1. Convince IBM to change their database driver to ignore GetACP() and directly retrieve the code page from the system registry. Or add utf8 support to the driver. Or use wide char API's if possible (define UNICODE, _UNICODE). Good luck with that unless you own the code 😊

 

2. Change the system code page to UTF-8. This might break both the existing database and other applications so possibly feasible only with brand new DB installs.

 

3. Set the DB2CODEPAGE environment variable to 1208 (UTF-8). The DB2 docs state "At execution time, the active code page of the user application when a database connection is made is in effect for the duration of the connection. All data is interpreted based on this code page; this includes dynamic SQL statements, user input data, user output data, and character fields in the SQLCA." Given this last, I am afraid this may misinterpret existing content in the database but do not really know. Also don’t know if this environment needs to be set systemwide or suffices for the TPC benchmark processes.

 

Perhaps folks on tcl-core may provide other suggestions.

 

Good luck

 

/Ashok

Re: [TCLCORE] [External] Tcl + Thread on macOS Sequoia: fatal fork() error

[da S. P. J <pet...@fl...>]

I brought this up on our work slack and it’s apparently been a thing since 2005. Lots of CoreFoundation is non-reentrant or and gets all higgledy-piggledy if you fork() without exec()ing.

https://developer.apple.com/library/archive/technotes/tn2083/_index.html#//apple_ref/doc/uid/DTS10003794-CH1-SUBSECTION64

From: Donald G Porter via Tcl-Core <tcl...@li...>
Date: Friday, February 28, 2025 at 07:44
To: Tcl List Core <tcl...@li...>
Subject: [External] [TCLCORE] Tcl + Thread on macOS Sequoia: fatal fork() error

I've received a report that some of our programs running on macOS
Sequoia 15.3.1 that are built on Tcl and Thread are failing with this
error:

    The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
    Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

Report is this problem occurs with both Tcl 8.6.16 and Tcl 9.0.0.

Before I start trying to chase it, is this a known problem and are there known remedies?

--
| Don Porter            Applied and Computational Mathematics Division |
| don...@ni...             Information Technology Laboratory |
| https://urldefense.com/v3/__http://math.nist.gov/*DPorter/__;fg!!MvWE!DoYL8v6qzic5MoC0p4aMJs0RTzP8DqLadKpKLR0xsei2VDExC5ywTdKVO8t5_BDzqH52HLLx0H6K7ZL2xgJW7qnFyfMmXT0ATw$<https://urldefense.com/v3/__http:/math.nist.gov/*DPorter/__;fg!!MvWE!DoYL8v6qzic5MoC0p4aMJs0RTzP8DqLadKpKLR0xsei2VDExC5ywTdKVO8t5_BDzqH52HLLx0H6K7ZL2xgJW7qnFyfMmXT0ATw$>                                   NIST |
|______________________________________________________________________|



_______________________________________________
Tcl-Core mailing list
Tcl...@li...
https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/tcl-core__;!!MvWE!DoYL8v6qzic5MoC0p4aMJs0RTzP8DqLadKpKLR0xsei2VDExC5ywTdKVO8t5_BDzqH52HLLx0H6K7ZL2xgJW7qnFyfMpgxaN5w$<https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/tcl-core__;!!MvWE!DoYL8v6qzic5MoC0p4aMJs0RTzP8DqLadKpKLR0xsei2VDExC5ywTdKVO8t5_BDzqH52HLLx0H6K7ZL2xgJW7qnFyfMpgxaN5w$>

Re: [TCLCORE] Question about permitted changes in patchlevel releases

[Donald G P. <don...@ni...>]

On 2/27/25 21:48, apnmbx-public--- via Tcl-Core wrote:
>
> Do Tcl versioning conventions allow functions to be added to the stubs table in a patch release, or does it require a minor release?
>

The normal practice has been that the public stubs table (and the declared public interface) does not grow in a patch release.

Occasionally we have departed from this, so if there's a good justification we can consider the pros & cons, but I think it's something that deserves some review.

-- 
| Don Porter            Applied and Computational Mathematics Division |
| don...@ni...             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|

[TCLCORE] Tcl + Thread on macOS Sequoia: fatal fork() error

[Donald G P. <don...@ni...>]

I've received a report that some of our programs running on macOS
Sequoia 15.3.1 that are built on Tcl and Thread are failing with this
error:

    The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
    Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

Report is this problem occurs with both Tcl 8.6.16 and Tcl 9.0.0.

Before I start trying to chase it, is this a known problem and are there known remedies?

-- 
| Don Porter            Applied and Computational Mathematics Division |
| don...@ni...             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|

[TCLCORE] Question about permitted changes in patchlevel releases

[<apn...@ya...>]

Do Tcl versioning conventions allow functions to be added to the stubs table
in a patch release, or does it require a minor release?

 

/Ashok

[TCLCORE] sqlite3 3.49.1 released

[Jan N. <jan...@gm...>]

The upstream SQLite project released 3.49.1 of SQLite recently

>From that, I derived the TEA-based Tcl package we layer
on top of it.

    http://cyqlite.sourceforge.net/cgi-bin/sqlite/timeline

That's now available as Tcl package sqlite3.49.1.tar.gz from

    https://sourceforge.net/projects/tcl/files/Tcl/8.6.16/
or
    https://sourceforge.net/projects/tcl/files/Tcl/9.0.1/

Unpack that source distribution in the "pkgs" subdir of your Tcl
8.6.x or 9.0.x source code distribution and run `make install`
again for your platform.
That will build and install the updated sqlite package.

Unless another SQLite release happens first, this package will be
bundled with Tcl 8.6.17 / Tcl 9.0.2

Regards,
     Jan Nijtmans

Re: [TCLCORE] Report of Tcl/Tk biweekly telco on 2025-02-25

[Harald O. <har...@el...>]

Yes, of cause, great idea.

Appreciation,
Harald

Am 25.02.2025 um 17:18 schrieb Reinhard Max:
> Am 25.02.2025 13:08, schrieb Harald Oehlmann:
> 
>> IMHO, UDP support should be in the core.
> 
> Shall we try to polish my new socket stuff to the point that it can go 
> into 9.1 at least as a preview under tcl::unsupported?
> 
>  From my POV all functionality is there to give it a try as an add-on 
> that is not meant to replace the [socket] command in the first run. But 
> I would like to have some discussion about design decisions for stuff 
> like the handling of symbolic constants.
> 
> cu
> Reinhard