News for hackers. Stuff that matters.
Re:Tcl the misunderstood (2006) by rotskoff on Friday December 14, 2012 @09:59AM (#4921184)
I use Tcl for a number of analysis scripts inside some scientific software. Recently, I came across a situation in which I had nested loops:

    for {set i 0} {$i<$n} {incr i} {
        # Some comment
        for {set j 0} {$j<$n} {incr j} {
The script refused to run and eventually I figured out that the comment was somehow impeding execution. I still don't understand why.
Re:Tcl the misunderstood (2006) by engtech on Friday December 14, 2012 @02:46PM (#4922880)
This also breaks, because comments are syntax.

   proc some_proc {a b} {
   
   } # some_proc
Re:Tcl the misunderstood (2006) by vorg on Saturday December 15, 2012 @11:26PM (#4927327)
Based on the instructions in the article (tho I haven't tried it out), putting a semicolon before the hash would work...

    proc some_proc {a b} {
    
    } ;# some_proc
Re:Tcl the misunderstood (2006) by ZoFreX on Saturday December 15, 2012 @11:25AM (#4925554)
That's easier to explain though - you are passing the arguments {a b} { } # and some_proc to the procedure some_proc. Because comments are just another command, the # has to be the first non-whitespace character on the line.
Re:Tcl the misunderstood (2006) by ZoFreX on Saturday December 15, 2012 @11:25AM (#4925557)
Are you sure the comment didn't have some curly brackets in it or something like that?