Groups | Search | Server Info | Login | Register
Groups > comp.lang.tcl > #55581
| From | meshparts <alexandru.dadalau@meshparts.de> |
|---|---|
| Newsgroups | comp.lang.tcl |
| Subject | Re: Very hard to debug issue |
| Date | 2026-03-18 21:28 +0100 |
| Message-ID | <10pf1th$8i9u$1@tota-refugium.de> (permalink) |
| References | (5 earlier) <10ocmog$36gn$1@dont-email.me> <10odvun$19lq5$1@tota-refugium.de> <10oepm6$ogb9$1@dont-email.me> <10of3ga$1af07$1@tota-refugium.de> <ygaldfsauzo.fsf@akutech.de> |
Am 16.03.2026 um 12:12 schrieb Ralf Fassel:
> * meshparts <alexandru.dadalau@meshparts.de>
> | thread::create -preserved "namespace eval ::meshparts {} {variable
> | sourceexe $sourceexe; variable sourcedir \"$sourcedir\"; variable
> | sourcefile \"$sourcefile\"}; thread::wait"
> --<snip-snip>--
> | I know I should have used "list" to build up the string, but in this
> | case there are those semicolons in the string ";" and I always have
> | issues combining ";" in the "list" command.
>
> thread::create -preserved \
> "namespace eval ::meshparts {} { \
> [list variable sourceexe $sourceexe];
> [list variable sourcedir $sourcedir];
> [list variable sourcefile $sourcefile];
> }; thread::wait"
>
> Or set the individual cmds via list, and combine as string:
> set cmd1 [list variable sourceexe $sourceexe]
> set cmd2 [list variable sourcedir $sourcedir]
> set cmd3 [list variable sourcefile $sourcefile]
> thread::create -preserved \
> "namespace eval ::meshparts {} { $cmd1 ; $cmd2 ; $cmd3 } ; thread::wait"
>
> HTH
> R'
Thanks, nice solution.
Back to comp.lang.tcl | Previous | Next — Previous in thread | Find similar
Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 09:03 +0100
Re: Very hard to debug issue undroidwish <undroidwish@googlemail.com> - 2026-03-04 10:12 +0100
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 12:35 +0100
Re: Very hard to debug issue Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-03-11 17:12 +0000
Re: Very hard to debug issue Ralf Fassel <ralfixx@gmx.de> - 2026-03-04 12:09 +0100
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 12:37 +0100
Re: Very hard to debug issue Christian Gollwitzer <auriocus@gmx.de> - 2026-03-04 21:26 +0100
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-05 07:25 +0100
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 12:40 +0100
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 12:41 +0100
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 12:42 +0100
Re: Very hard to debug issue Rich <rich@example.invalid> - 2026-03-04 13:05 +0000
Re: Very hard to debug issue et99 <et99@rocketship1.me> - 2026-03-04 17:09 -0800
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-05 07:19 +0100
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-05 07:20 +0100
Re: Very hard to debug issue Rich <rich@example.invalid> - 2026-03-05 13:29 +0000
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-05 16:43 +0100
Re: Very hard to debug issue Rich <rich@example.invalid> - 2026-03-05 17:02 +0000
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-05 16:45 +0100
Re: Very hard to debug issue et99 <et99@rocketship1.me> - 2026-03-05 11:49 -0800
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-06 08:32 +0100
Re: Very hard to debug issue Rich <rich@example.invalid> - 2026-03-06 14:51 +0000
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-06 18:39 +0100
Re: Very hard to debug issue Ralf Fassel <ralfixx@gmx.de> - 2026-03-16 12:12 +0100
Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-18 21:28 +0100
csiph-web