[Tcl-bugs] [ tcl-Bugs-3004191 ] glob - the use of [try] does not set msg prober

[SourceForge.net <no...@so...>]

Bugs item #3004191, was opened at 2010-05-19 19:08
Message generated for change (Comment added) made by johannes-kuhn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=3004191&group_id=10894

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: 33. Safe Base
Group: development: 8.6b1.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Johannes Kuhn (johannes-kuhn)
Assigned to: Donal K. Fellows (dkf)
>Summary: glob - the use of [try] does not set msg prober

Initial Comment:
(bin) 52 % safe::createInterp slave; slave eval {glob *}
invalid command name "safe::createInterp"

Please trap the ok too :)

Patch file included.

----------------------------------------------------------------------

>Comment By: Johannes Kuhn (johannes-kuhn)
Date: 2010-05-20 14:32

Message:
    try {
	::interp invokehidden $slave glob {*}$cmd
    } on error msg {
	Log $slave $msg
	return -code error "script error"
    }

As we can see, the result of glob is not used unless an error occurs.
But the statement
    Log $slave "GLOB @ $msg" NOTICE
requires that $msg is set. We use $msg also for the result of [glob]
later.
My solution is to catch ok too, but we can also use the old [catch] or set
msg [glob].

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=3004191&group_id=10894