f



Bug789040 came back in Tcl 8.4.6 and Tcl 8.5.

Dear All,

Bug 789040 caused exec error in Windows 9x and was fixed in 10/04/03. 
But it came back in Tcl 8.4.6 and Tcl 8.5.  Tcl Windows 9x users
should be alerted to the possible failure of exec in the current Tcl
8.4.6 and 8.5 releases due to this bug.

Chengye Mao

http://www.geocities.com/~chengye
0
5/10/2004 1:20:09 AM
comp.lang.tcl 23429 articles. 2 followers. Post Follow

5 Replies
1039 Views

Similar Articles

[PageSpeed] 20

Chengye Mao wrote:
> Bug 789040 caused exec error in Windows 9x and was fixed in 10/04/03. 
> But it came back in Tcl 8.4.6 and Tcl 8.5.  Tcl Windows 9x users
> should be alerted to the possible failure of exec in the current Tcl
> 8.4.6 and 8.5 releases due to this bug.

Have you identified at what point it was reintroduced?  Was the
fix causing other issues and reverted, or simply reintroduced by
accident?

-- 
     Jeff Hobbs, The Tcl Guy
     http://www.ActiveState.com/, a division of Sophos
0
jeffh (1291)
5/10/2004 2:50:00 AM
Jeff Hobbs <jeffh@activestate.com> wrote in message news:<409EEDB5.40905@activestate.com>...
> Chengye Mao wrote:
> > Bug 789040 caused exec error in Windows 9x and was fixed in 10/04/03. 
> > But it came back in Tcl 8.4.6 and Tcl 8.5.  Tcl Windows 9x users
> > should be alerted to the possible failure of exec in the current Tcl
> > 8.4.6 and 8.5 releases due to this bug.
> 
> Have you identified at what point it was reintroduced?  Was the
> fix causing other issues and reverted, or simply reintroduced by
> accident?

Reintroduced in rev. 1.41 of tclWinPipe.c in Feb, 2004. The bug was a
missing space between tclpip.dll and the following command. The fix
simply added the required space to solve this problem. I could not see
any issues that the fix could possiblly have and don't understand why
it should be replaced by the old buggy code.  I guess it was probably
reverted accidentently.

Chengye
0
5/10/2004 5:33:39 AM
Chengye Mao wrote:
>> > Bug 789040 caused exec error in Windows 9x and was fixed in 10/04/03. 
>> > But it came back in Tcl 8.4.6 and Tcl 8.5.  Tcl Windows 9x users
>> > should be alerted to the possible failure of exec in the current Tcl
>> > 8.4.6 and 8.5 releases due to this bug.
 
Jeff Hobbs ...
>> Have you identified at what point it was reintroduced?  Was the
>> fix causing other issues and reverted, or simply reintroduced by
>> accident?
 
Chengye Mao wrote:
> Reintroduced in rev. 1.41 of tclWinPipe.c in Feb, 2004. The bug was a
> missing space between tclpip.dll and the following command. The fix
> simply added the required space to solve this problem. I could not see
> any issues that the fix could possiblly have and don't understand why
> it should be replaced by the old buggy code.  I guess it was probably
> reverted accidentently.

I see you re-fixed 789040 in revision 1.44; this should also be
done on the core-8-4-branch if Tcl 8.4.7 is to also be corrected.

Of greater concern to me is whether David Gravereaux agrees with
this change, and we've now reached a stable solution, or whether
you'll continue a tug-o-war over BuildCommandLine() .  :(

-- 
| Don Porter          Mathematical and Computational Sciences Division |
| donald.porter@nist.gov             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|
0
dgp1 (946)
5/10/2004 2:27:14 PM
Don Porter <dgp@email.nist.gov> wrote:

>Of greater concern to me is whether David Gravereaux agrees with
>this change, and we've now reached a stable solution, or whether
>you'll continue a tug-o-war over BuildCommandLine() .  :(

Confusion is best fixed with commenting of the source for those non-obvious
things.  Now it's obvious.  The only way to hit the "need to prime" logic on NT
is to execute a 16-bit DOS app under Tk.  And the part that primes the cmdLine
DString already appends a space:

win/tclWinPipe.c:1161 ::
	    Tcl_DStringAppend(&cmdLine, "cmd.exe /c ", -1);

I'll remove that space as BuildCommandLine() will be doing this.
-- 
David Gravereaux <davygrvy@pobox.com>
[species: human; planet: earth,milkyway(western spiral arm),alpha sector]
0
davygrvy (1376)
5/10/2004 8:49:17 PM
Don Porter <dgp@email.nist.gov> wrote in message news:<slrnc9v4a2.p3f.dgp@clover.cam.nist.gov>...
> Chengye Mao wrote:
> >> > Bug 789040 caused exec error in Windows 9x and was fixed in 10/04/03. 
> >> > But it came back in Tcl 8.4.6 and Tcl 8.5.  Tcl Windows 9x users
> >> > should be alerted to the possible failure of exec in the current Tcl
> >> > 8.4.6 and 8.5 releases due to this bug.
>  
> Jeff Hobbs ...
> >> Have you identified at what point it was reintroduced?  Was the
> >> fix causing other issues and reverted, or simply reintroduced by
> >> accident?
>  
> Chengye Mao wrote:
> > Reintroduced in rev. 1.41 of tclWinPipe.c in Feb, 2004. The bug was a
> > missing space between tclpip.dll and the following command. The fix
> > simply added the required space to solve this problem. I could not see
> > any issues that the fix could possiblly have and don't understand why
> > it should be replaced by the old buggy code.  I guess it was probably
> > reverted accidentently.
> 
> I see you re-fixed 789040 in revision 1.44; this should also be
> done on the core-8-4-branch if Tcl 8.4.7 is to also be corrected.
> 
> Of greater concern to me is whether David Gravereaux agrees with
> this change, and we've now reached a stable solution, or whether
> you'll continue a tug-o-war over BuildCommandLine() .  :(

David has modified the code with a better solution and I am very pleased.

Chengye
0
5/10/2004 10:29:41 PM
Reply:

Similar Artilces:

"::tcl::tm::UnknownHandler ::tclPkgUnknown msgcat 1.4" caused by replacing Tcl 8.4.1 with 8.5.7
In the blog http://planet.larrythecow.org/archives/2009-07-26.html "The Twouble with Tcl" Iain Buchanan shows that redefining OPEN proc leads to the errors similar to what I am getting - when I replaced Tcl 8.4.1 with Tcl 8.5.7. In my case I don't know the exact root cause though ... Any ideas how I should proceed with debugging this issue ? Thanks, Alex tclsh c:/Tornado/host/resource/hutils/tcl/makeSymTbl.tcl ppc tmp.o symTbl.c invalid command name "::tcl::tm::UnknownHandler" while executing "::tcl::tm::UnknownHandler ::tclPkgUnknown msg...

Binary reader speed comparison
I have a fairly simple binary reader proc that exhibits massive speed differences between Tcl 8.5.8 and Tcl8.6b1.1. Here's the proc: proc readFormatted {filename} { set fd [ open $filename r ] fconfigure $fd -encoding binary -translation binary binary scan [ read $fd 2 ] cc type nextlen if {$type != 75} { return -error "File is not in the expected format" } while {![append buffer [read $fd $nextlen] ; eof $fd]} { binary scan [read $fd 2] cc lastlen nextlen # convert to unsigned value set nextlen ...

tcl 8.4 to 8.5
Hi all, I've been using tcl 8.4.19 for ages, but just got moved to 8.5.11 at work, and now a lot of my scripts fail. For instance, I use: "package require aes" but this gets thrown out by 8.5 I need an idiots guide to upgrading, anyone help please? On 05/21/2013 01:25 PM, nivparsons wrote: > I've been using tcl 8.4.19 for ages, but just got > moved to 8.5.11 at work, and now a lot of my scripts fail. > > For instance, I use: > > "package require aes" > > but this gets thrown out by 8.5 Are your packages installed where both a Tcl 8.4 and a Tcl 8.5 installation can find them? As general advice, reporting verbatim error messages is often very helpful in getting more useful help. -- | Don Porter Applied and Computational Mathematics Division | | donald.porter@nist.gov Information Technology Laboratory | | http://math.nist.gov/~DPorter/ NIST | |______________________________________________________________________| On 05/21/2013 01:25 PM, nivparsons wrote: > I've been using tcl 8.4.19 for ages, but just got > moved to 8.5.11 at work, and now a lot of my scripts fail. Have you built/installed from source, or are you using binary distributions from some provider? What provider? -- | Don Porter Applied and Computational Mathematics Division | | donald.porter@nist.gov Information Technolog...

TCL is not thread safer in TCL 8.3 or 8.4... Any plans to fix this?
It is a shame that I can't upgrade one of my applications due to this problem, though the memory leaks also intorduced in 8.3 and 8.4 are problem as well. :( I have a process that spawn a configurable number of thread with a TCL intrepeter in each one. The interps are isolated and do not communicate or share anything withe each other. Each thread is a rule processor that is handed TCL scripts based on what events occurs within a multi process enviroment rnaing across the whole itnerprize... Works great with TCL 8.2, not a single problem... But with TCL 8.3 and TCL 8.4 we get quite a few run time errors and/or data corruption and core dumps that all leads back to TCL. :( Quite a shame! cwhooks@landacorp.com wrote: > It is a shame that I can't upgrade one of my applications due to this > problem, though the memory leaks also intorduced in 8.3 and 8.4 are > problem as well. :( What are the bug report ID numbers of the issues giving you trouble? -- | Don Porter Mathematical and Computational Sciences Division | | donald.porter@nist.gov Information Technology Laboratory | | http://math.nist.gov/~DPorter/ NIST | |______________________________________________________________________| Don Porter <dgp@email.nist.gov> wrote: > cwhooks@landacorp.com wrote: >> It is a shame that I can't upgrade one of my applications due to this >> problem, though the memory leaks also intorduced ...

tcl 8.5/8.4 difference
Hi TCLers, I've found a strange behaviour in Tcl 8.5.7 and 8.5.5 (vs. 8.4.19) when working with Pgtcl (pgaccess.tcl). The effected code line is (after a successfull database select): pg_result $pgres -assign curr_tabs The variable $pgres contains the correct handle (e.g. "pgsql6.0"), but Tcl 8.5 crashes with the message: Tcl_SetIntObj called with shared object whereas Tcl 8.4 continues without any error. I know that it is hard to analyze this problem without code, examples, .... but maybe the error behaviour brings some 1st idea where to start the search. I will investigate the problem more deeply. Found on Linux 64/32. -- Gerhard Reithofer Tech-EDV Support Forum - http://support.tech-edv.co.at On Aug 18, 7:11=A0am, Gerhard Reithofer <gerhard.reitho...@tech- edv.co.at> wrote: > Hi TCLers, > I've found a strange behaviour in Tcl 8.5.7 and 8.5.5 (vs. 8.4.19) when > working with Pgtcl (pgaccess.tcl). > > The effected code line is (after a successfull database select): > =A0 pg_result $pgres -assign curr_tabs > > The variable $pgres contains the correct handle (e.g. "pgsql6.0"), but > Tcl 8.5 crashes with the message: > > =A0 Tcl_SetIntObj called with shared object > > whereas Tcl 8.4 continues without any error. > > I know that it is hard to analyze this problem without code, examples, > ... but maybe the error behaviour brings some 1st idea where to start > the search. Does ...

regsub in tcl 8.5 and 8.6
parse this row set a "123(qwe)" in tcl 8.6 # regsub -all "\\(.*" $a "" 123qwe) in tcl 8.5 # regsub -all "\\(.*" $a "" 123 What to do ? Thank you for the report. Confirmed with 8.5.16 and 8.6.2 Aparently, 8.6 is not as greedy as 8.5. I don't know if this is a bug or a feature. Could you please register a bug report at: core.tcl.tk/tcl -> Login as anonymous -> New ticket The most important people don't read clt but read bug reports... Thank you, Harald 0L/QvtC90LXQtNC10LvRjNC90LjQuiwgOCDRgdC10L3RgtG...

Tcl 8.4 vs 8.5
This is OK in 8.5: expect1.3> set a {1 2 3} 1 2 3 expect1.4> expr {[lindex $a 1] in {2 3 4}} 1 But not OK in 8.4: expect1.8> set a {1 2 3} 1 2 3 expect1.10> expr {[lindex $a 1] in {2 3 4}} syntax error in expression "[lindex $a 1] in {2 3 4}": extra tokens at end of expression while compiling "expr {[lindex $a 1] in {2 3 4}}" Is there a way to make the expression backward compatible in 8.4? /WT On Feb 5, 10:16=A0pm, Why Tea <ytl...@gmail.com> wrote: > This is OK in 8.5: > expect1.3> set a =A0{1 2 3} > 1 2 3 > expect1.4> expr {[lindex $a 1] in {2 3 4}} > 1 > > But not OK in 8.4: > expect1.8> set a {1 2 3} > 1 2 3 > expect1.10> expr {[lindex $a 1] in {2 3 4}} > syntax error in expression "[lindex $a 1] in {2 3 4}": extra tokens at en= d of expression > =A0 =A0 while compiling > "expr {[lindex $a 1] in {2 3 4}}" > > Is there a way to make the expression backward compatible in 8.4? Though the error message was not that clear (expr error reporting has improved since then), the truth is just that "in" was not there yet :D An equivalent working in older Tcls: expr {[lsearch -exact {2 3 4} [lindex $a 1]]>=3D0} -Alex On Monday, February 6, 2012 10:50:05 AM UTC+11, Alexandre Ferrieux wrote: > On Feb 5, 10:16=A0pm, Why Tea <ytl...@gmail.com> wrote: > > This is OK in 8.5: > > expect1.3> set a =A0{1 2 3} > > 1 2 3 >...

tcl/tk 8.5 side 8.4
Hello i run windows vista familiy. I code with Tcl/Tk 8.4 with no problem. I would like to know if i can install Tcl/Tk 8.5 to test certain new possibilities without un-installing Tcl/Tk 8.4 ? thank you for help jerome groupeCompteRendu@gmail.com wrote: > Hello > i run windows vista familiy. I code with Tcl/Tk 8.4 with no problem. > I would like to > know if i can install Tcl/Tk 8.5 to test certain new possibilities > without un-installing > Tcl/Tk 8.4 ? > thank you for help > jerome Yes -- +------------------------------------------------------------------------+ | Gerald W. Lester | |"The man who fights for his ideals is the man who is alive." - Cervantes| +------------------------------------------------------------------------+ ...

Incr Tcl /Tk for Tcl 8.4
Hi, I am trying to download incr Tcl and incr Tk for Tcl/Tk 8.4.19. I looked at: http://sourceforge.net/projects/incrtcl/files/%5BIncr%20Tcl_Tk%5D-source/3.4.1/ But only itcl seems to be there. And the CVS doesn't have the 3.4.1 tag. Do you know where I can get incr Tk and hopefully a corresponding iwidgets? Thanks, Andres On 5 Okt., 11:16, Andres Garcia <tclc...@gmail.com> wrote: > Hi, > > I am trying to download incr Tcl and incr Tk for Tcl/Tk 8.4.19. > > I looked at: > > http://sourceforge.net/projects/incrtcl/files/%5BIncr%20Tcl_Tk%5D-sou... > > But only itcl seems to be there. And the CVS doesn't have the 3.4.1 > tag. There is no tag for this version. But you can use a date. cvs -d :pserver:anonymous@incrtcl.cvs.sourceforge.net:/cvsroot/incrtcl -z3 co -P -D 2010-10-28 incrTcl > > Do you know where I can get incr Tk and hopefully a corresponding > iwidgets? Itk is inside itcl sources. cvs -d :pserver:anonymous@incrtcl.cvs.sourceforge.net:/cvsroot/incrtcl -z3 co -P -D 2010-10-28 iwidgets HTH rene Thanks. Andres >> I am trying to download incr Tcl and incr Tk for Tcl/Tk 8.4.19. >> >> I looked at: >> >> http://sourceforge.net/projects/incrtcl/files/%5BIncr%20Tcl_Tk%5D-sou... >> >> But only itcl seems to be there. And the CVS doesn't have the 3.4.1 >> tag. The released sources for Itcl 3.4.1 were not developed in SF CVS. SF CVS got abandoned during the January...

Tcl 8.4.x & tcl-dp 4.0.x
Has anyone built tcl-dp 4.0.x on windows against Tcl 8.4.x ? Is it possible to get the windows dll and the source code with modifications? ...

Linux font issue between tcl 8.4 and 8.5?
We are using a red hat version of linux as well as activetcl 8.4 and 8.5 in one situation. A developer pointed out to me that when he looks at activetcl 8.4, there are a large number of fonts available. But when he looks at the same machine, same login, in a activetcl 8.5 process, it only sees a small number of fonts. I presume this has something to do with the new truetype font support. Is there something special one has to do with tk 8.5 so that it also sees the non-truetype fonts? On the linux system we are using, the number of truetype fonts is pretty limited and applications do not look as nice as the same applications running against activetcl 8.4. So, we are looking for suggestions on dealing with 8.5's font handling situation. On Jan 20, 2:12=A0pm, "Larry W. Virden" <lvir...@gmail.com> wrote: > We are using a red hat version of linux as well as activetcl 8.4 and > 8.5 in one situation. A developer pointed out to me that when he looks > at activetcl 8.4, there are a large number of fonts available. But > when he looks at the same machine, same login, in a activetcl 8.5 > process, it only sees a small number of fonts. > > I presume this has something to do with the new truetype font support. > Is there something special one has to do with tk 8.5 so that it also > sees the non-truetype fonts? > So, we are looking for suggestions on dealing with 8.5's font handling > situation. You could recompile with --disabl...

bind <Shift-something> does not work under XF 4.3 tcl 8.3.5, ActiveState 8.4.3
I have tried the following script, under XFree86-4.3.0-2 both with RedHat 8 and 9, either with the native RH tcl 8.3.5 and with the ActiveState tcl 8.4.3 distributions. In all these platform combinations, the binding of <Shift-* does not work. For example, for Shift-F1, I get XF86_Switch_VT_1 (see xmodmap dump below), but the binded script is not triggered. However, the script works fine under Windows, with the same tcl distributions. Any hint? pack [entry .a] bind .a <Shift_L> {puts "hello, Shift"} bind .a <Shift-F1> {puts "hello, Shift-F1"} bind .a <Shift-Tab> {puts "hello, Shift-Tab"} bind .a <Control_L> {puts "hello, Control"} bind .a <Control-F1> {puts "hello, Control-F1"} bind .a <Control-Tab> {puts "hello, Control-Tab"} xmodmap -pk There are 4 KeySyms per KeyCode; KeyCodes range from 8 to 255. KeyCode Keysym (Keysym) ... Value Value (Name) ... 8 9 0xff1b (Escape) 10 0x0031 (1) 0x0021 (exclam) 11 0x0032 (2) 0x0022 (quotedbl) 12 0x0033 (3) 0x00b7 (periodcentered) 13 0x0034 (4) 0x0024 (dollar) 14 0x0035 (5) 0x0025 (percent) 15 0x0036 (6) 0x0026 (ampersand) 16 0x0037 (7) 0x002f (slash) 17 0x0038 (8) 0x0028 (parenleft) 18 0x0039 (9) 0x0029 (parenright) 19 0x0030 (0) 0x003d (equal) 20 0x0027 (apostrophe) 0x003f (question) ...

'lrange' differences in tcl 8.4 and 8.6
Hi, lrange works differently in tcl versions 8.4 and 8.6, if the output has only #. % info patch 8.4.13 % % set test {a "#"} a "#" % set testme [lrange $test 1 end] # % info patch 8.6.1 % set test2 {a "#"} a "#" % set testme [lrange $test2 1 end] {#} Is this an intentional change ? Most of our regression scripts are failing after upgrade to 8.6.1, as the regular expressions don't match, as lrange was earlier returning #, but after upgrade {#} Regards, Lucky Lucky Y <ylucki@gmail.com> wrote: > Hi, >...

Tcl SOAP
OK - Believe it or not, I have a "requirement" to use SOAP! The last time I worked with this, it did not work at all. So the following quesitons come to mind: Has it improved any - and it is working on Tcl 8.4.1 or later? Anyone using it for connecting to Web Services? Anyone using it to provide Web Services? I will immediately need to connect to a Web Service using SOAP (this is the "only" option), and then later provide Web Services via Apache (1.3 likely, but will migrate to 2.0x if necessary). Any guidance or suggestions would be most welcomed! Dave In article <e45f1db4.0405281105.8d1b86e@posting.google.com>, Dave Bigelow <davidhbigelow@simplifiedlogic.com> wrote: >OK - > >Believe it or not, I have a "requirement" to use SOAP! > >The last time I worked with this, it did not work at all. So the >following quesitons come to mind: > >Has it improved any - and it is working on Tcl 8.4.1 or later? >Anyone using it for connecting to Web Services? >Anyone using it to provide Web Services? > >I will immediately need to connect to a Web Service using SOAP (this >is the "only" option), and then later provide Web Services via Apache >(1.3 likely, but will migrate to 2.0x if necessary). > >Any guidance or suggestions would be most welcomed! > >Dave Short answer: yes. What does "immediately" mean to you? What platforms interest you? I'm working with t...

Oratcl 4.4 : Tcl 8.5 tested against Oracle 11g (11.1.0.6.0) Linux x86
Hot off the press. Oratcl 4.4 (and the CVS head). Have just been run/tested against Oracle 11g and all the tests in the test suite have passed. No special configurations required other than the traditional ORACLE_HOME env. variable being set. -Todd On Aug 15, 3:45 pm, "thelf...@gmail.com" <thelf...@gmail.com> wrote: > Hot off the press. > > Oratcl 4.4 (and the CVS head). Have just been run/tested against > Oracle 11g and all the tests in the test suite have passed. > > No special configurations required other than the traditional > ORACLE_HOME env. variable being set. > > -Todd Very cool...we are going to Blade servers at work but only 10g but it is good to know that it works with 11g as well. Robert P.S. Have you updated the Oratcl site lately? ; ) On Aug 15, 9:23 pm, Robert Hicks <sigz...@gmail.com> wrote: > On Aug 15, 3:45 pm, "thelf...@gmail.com" <thelf...@gmail.com> wrote: > > > Hot off the press. > > > Oratcl 4.4 (and the CVS head). Have just been run/tested against > > Oracle 11g and all the tests in the test suite have passed. > > > No special configurations required other than the traditional > > ORACLE_HOME env. variable being set. > > > -Todd > > Very cool...we are going to Blade servers at work but only 10g but it > is good to know that it works with 11g as well. > > Robert > > P.S. Have you updated the Oratcl s...

Tcl 8.4.4 SunOS 5.5.1 failed tests
Hello, I tried out tcl 8.4.4 $ uname -a SunOS pegasus 5.5.1 Generic_103640-31 sun4u sparc SUNW,Ultra-1 $ cd tcl8.4.4/unix $ ./configure --disable-shared --enable-gcc --disable-load $ make $ make test The follwoing tests failed. Are other people having the same failed tests or I need to install/upgrade something. Thanks in advance ... -------------------------------------------------------------------------------- ==== event-13.8 Tcl_WaitForFile procedure, waiting indefinitely FAILED ==== Contents of test case: set f [open "|sleep 2" r] set result "" lappend result [testfilewait $f readable 100] lappend result [testfilewait $f readable -1] close $f set result ---- Test generated error; Return code was: 1 ---- Return code should have been one of: 0 2 ==== event-13.8 FAILED exec.test execute.test expr-old.test expr.test fCmd.test ==== fCmd-12.7 renamefile: renaming directory into offspring FAILED ==== Contents of test case: catch {file delete -force -- tfad} file mkdir tfad file mkdir tfad/dir set result [catch {file rename tfad tfad/dir}] file delete -force tfad set result ---- Result was: 0 ---- Result should have been (exact matching): 1 ==== fCmd-12.7 FAILED ==== io-35.5 Tcl_Eof, eof detection on nonblocking pipe FAILED ==== Contents of test case: removeFile pipe set f [open $path(pipe) w] puts $f { exit } close $f set f [open "|[list [interpreter] $p...

Strange difference between Tcl/Tk 8.4.12 and 8.5.0
Hi, there is a difference between etcl.exe Tcl/Tk 8.4.12 activestate tcl 8.5.0.0-beta-5 on the calc.tcl demo that comes with the etcl download. In 8.5: sqrt(2) --> 213562 ... (No problems with numbers that have non-negative integer square roots) 8.4 was fine. This is obviously not a problem with 8.5. Rather there is some difference between the parsers that is resulting in different arguments being sent to the sqrt function. Perhaps someone more knowledgeable can look at the calc.tcl demo. Regards bobsteel a �crit : > Hi, there is a difference between > > etcl.exe Tcl/Tk 8.4.12 > activestate tcl 8.5.0.0-beta-5 > > on the calc.tcl demo that comes with the etcl download. > > In 8.5: sqrt(2) --> 213562 ... > (No problems with numbers that have non-negative integer square roots) > 8.4 was fine. > > This is obviously not a problem with 8.5. Rather there is some > difference between the parsers that is resulting in different arguments > being sent to the sqrt function. Perhaps someone more knowledgeable can > look at the calc.tcl demo. > Reason is much simpler. It's because with 8.5, tcl_precision default to 0 (i.e. maximal precision) while it defaults to 12 with 8.4.x (eTcl or any other distrib). This calc.tcl demo in eTcl distrib is pretty simple (not to say trivial), and implicitely use this for number formatting, instead of explictely calling [format ...] to format displayed result. This can of course b...

difference between tcl 8.4.2 & 8.4.4
% exec $env(COMSPEC) /c net config This command now fails on Tcl 8.4.4 What can I do instead? to run with either version of tcl and windows 98. "couldn't execute "C:\WINDOWS\COMMAND.COM": no such file or directory" Running on Win 98. Win XP is ok. Peter Campbell wrote: > % exec $env(COMSPEC) /c net config > > This command now fails on Tcl 8.4.4 > What can I do instead? to run with either version of tcl and windows 98. > > "couldn't execute "C:\WINDOWS\COMMAND.COM": no such file or directory" > > Running on Win 98. > Win XP is ok. This is a known bug that is already fixed. 8.4.5 will be out by the end of the week with this corrected. -- Jeff Hobbs, The Tcl Guy http://www.ActiveState.com/, a division of Sophos Hi Peter, Peter Campbell <pc@acs.co.nz> writes: > % exec $env(COMSPEC) /c net config > > This command now fails on Tcl 8.4.4 > What can I do instead? to run with either version of tcl and windows 98. > > "couldn't execute "C:\WINDOWS\COMMAND.COM": no such file or > directory" > > Running on Win 98. > Win XP is ok. This was discussed recently, check google. IIRC, this is a bug in 8.4.4, to be fixed in 8.4.5. benny ...

upgrade problem tcl/tk-8.4 -> 8.5 -- please help
Hi, unfortunately I have next to no knowledge in Tcl. When upgrading from Tcl/Tk-8.4.* to 8.5.3 an error occurs in an old script (tkdiff+) I get unmatched open brace in list unmatched open brace in list while executing "foreach {pattern dummy1 dummy2} $content { if {$pattern == $data(v:status:pattern)} { set content [lreplace $content $i $i [clock format [clock s..." where $content contains (many lines removed) /Src/Src/Tcl/tkdiff-4.1.3-unix|/Src/Src/Tcl/tkdiff-4.1.4-unix {Sat Mar 08 16:20:58 CET 2008} { directory:. none directory:.. none file:COPYING none file:Changelog nok file:tkdiff nok file:tkdiff.bck none } /home/jarausch/Python_My/BackUp_X|/numa-i/home/jarausch/Python_My/BackUp_OLD {Tue May 20 14:39:37 CEST 2008} { directory:. none directory:.. none file:AFS_Launch.C none file:BackUp.Config none directory:jarausch ...

tcl 8.4.8 bugs?
Is this a bug in tcl8.4.8? tclsh % set test_string "</Config>" </Config> % if [ regexp "^</(.*)>" $test_string jerk cfg_line ] { puts $cfg_line } elseif [ regexp "^<(.*)>" $test_string jerk cfg_line ] { } /Config % if [ regexp "^</(.*)>" $test_string jerk cfg_line ] { puts $cfg_line } elseif [ regexp "^<(.*)>" $test_string jerk cfg_line2 ] { } Config % In article <5b2f12a6.0411301212.6811fd48@posting.google.com>, Xiaofeng Wu wrote: > Is this a bug in tcl8.4.8? No. > tclsh > % set test_string "</Config>" ></Config> > % if [ regexp "^</(.*)>" $test_string jerk cfg_line ] { > puts $cfg_line > } elseif [ regexp "^<(.*)>" $test_string jerk cfg_line ] { > } > /Config Notice that you have not braced the expressions in your [if] command. This means all of them will be evaluated. All substitutions are done before command evaluation. You probably wanted to code this instead: % set test_string "</Config>" </Config> % if {[ regexp "^</(.*)>" $test_string jerk cfg_line ]} { puts $cfg_line } elseif {[ regexp "^<(.*)>" $test_string jerk cfg_line ]} { } Config The difference is very basic to understanding the Tcl language. If you do not understand, take some time to review Tcl's substitution rules again. -- | Don Porter Mathematical and Compu...

ANNOUNCE: freeWrap 6.4 (for TCL 8.5) released
This message announces the release of freeWrap version 6.4 The freeWrap program turns TCL/TK scripts into single-file binary executable programs. freeWrap can wrap TCL/TK applications that consist of multiple script and binary files. FreeWrap combines all the files together into a single executable file. freeWrap 6.4 is based on TCL/TK 8.5.0 freeWrap executables are freely available for both Linux and Windows. Instructions and source code for building freeWrap on both Windows and UNIX platforms is included in the documentation. The following additional variations of freeWrap are also available for download: freewrapPLUS a windowing application that includes TCL/TK along with the tkTable and SQLite extensions freewrapTCLSH a console-only application which includes only TCL. Please visit the freeWrap home page: http://freewrap.sourceforge.net Changes implemented in version 6.4 ------------------------------------ 1. This is the first version of freeWrap based on TCL/TK 8.5.0. 2. Unlike previous versions, freewrapPLUS 6.4 does not contain the BLT extension since BLT is not yet compatible with TCL/TK 8.5. 3. The makefile for Windows has been modified to use Microsoft Visual C++ 8.0 Express Edition. ...

Compiling Tcl 8.4.8
Just finish compiling Tcl 8.4.8 in WinXP. It produced few more files that 8.2, like tcl84s.lib, tclsh84s.exe.. What are those letter after the version number mean?? In this case, the 's' after 84. I was not be able get any info by searhing google... Can anyone please point me to a place where we I can understand those letter means... I think it means "static". I suppose these libs can be used for embedding tcl into other applications, without depending on the tcl dlls. George "Ming" <chung.ming.chan@gmail.com> wrote in message news:83573a77.0412011235.46e835bd@posting.google.com... > Just finish compiling Tcl 8.4.8 in WinXP. > It produced few more files that 8.2, like tcl84s.lib, tclsh84s.exe.. > > What are those letter after the version number mean?? > In this case, the 's' after 84. > > I was not be able get any info by searhing google... > > Can anyone please point me to a place where we I can understand those > letter means... ...

ANNOUNCE: Tcl/Tk 8.4.8 rpm specification with thread 2.5.2 extension
http://jfontain.free.fr/tcltk-8.4.8-1.spec Generated and tested on an up-to-date Red Hat Fedora Core 3 i386 system. The rpms can install under /opt/tcltk (see notes below) in order not to conflict and peacefully coexist with the stock Redhat Tcl and Tk rpms. To build the rpms, download the Tcl/Tk 8.4.8 and Thread 2.5.2 sources from http://download.sourceforge.net/tcl/ into the /usr/src/redhat/SOURCES/ directory, place the specification file in the /usr/src/redhat/SPECS/ directory, then from that directory, type: # rpmbuild -bb --clean tcltk-8.4.8-1.spec Notes: - You may change the installation directory and turn on the thread extension at the beginning of the specification file. -- Jean-Luc Fontaine mailto:jfontain@free.fr http://jfontain.free.fr/ ...

CatOS 6.4 came after 8.5
We just got a couple of new 6509's, and they shipped with catos 6.4.23. This didn't make sense to me since 8 has been shipping for a few years. Yet, I checked cisco's download site, and sure enough 6.4.23 was released December 21, 06, and 8.5.8 was released December 5, 2006. The image size for 6.4 is quite a bit less that 8.5, but new switches came with 6.4. Is 6.4 a new train or something? "Bitswapper" <john@johnsdomain.org> wrote in message news:1170278856.240066.317660@v45g2000cwv.googlegroups.com... > We just got a couple of new 6509's, and they sh...

Web resources about - Bug789040 came back in Tcl 8.4.6 and Tcl 8.5. - comp.lang.tcl

Resources last updated: 3/13/2016 7:36:35 PM