Juergen, how did you decide what to return as a Tcl
diagnostic, and what to send directly to stderr?
Here's the proximate inspiration of my question: I'm
on a platform which doesn't support multi-casting. I've
written a Scotty application (I'm fudging the details in
small ways which are not material to this discussion).
What my users see when they launch is a "straps: unable
to join multicast group: Invalid argument". It scares
them. I know it's only a diagnostic, but it's hard com-
municating that to them. I can't conveniently filter
it, because you're writing it directly to stderr, so
it's un-catch-able.
I could modify the Scotty sources, or I could even write
my own extension to turn stderr off and on. Compared to
those alternatives, I'd rather talk to my customers.
Juergen, I see in the 2.1.5 sources 213 instances of
"fprintf(stderr, ..." Do you understand the challenge
this presents me? Can you give me any advice on this
subject?
Cameron Laird http://starbase.neosoft.com/~bodi/nesi.html
Network Engineered Solutions +1 713 763 8366
claird@NeoSoft.com +1 281 996 8546 FAX
Houston WWW Business Guide: http://starbase.neosoft.com/~bodi/HouGuide.html
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.