| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Corrected error in handling of catch contexts to prevent crash with
chained handlers.
|
|
|
|
|
|
|
|
| |
not result in a *guaranteed* push of a Tcl_Obj on the stack, we must
push an empty object. Otherwise it is possible to get to a 'concat1'
or 'done' without enough values on the stack, resulting in a crash.
Thanks to Joe Mistachkin for identifying a script that could trigger
this case.
|
| |
|
|
|
|
| |
exactly the same as the one in "return"
|
| |
|
| |
|
|
|
|
|
| |
of an instruction! Tightened the instruction issuing. Moved endCatch
calls closer to their point that they guard.
|
|
|
|
|
|
|
|
| |
* use do { ... } while (0) in macros
* avoid shadowing one local variable with another
* use clearer 'foo.bar++;' instead of '++foo.bar;' where result not
required (i.e., semantically equivalent)
* follow Engineering Manual rules on spacing and declarations
|
|
|