- "This application has requested the Runtime to terminate it in an unusual
way" A standing rule on the MicrosoftOS seems to require system-messages
to be as cryptic and unhelpfull as possible. Still without a bright and
insightfull closure this thread could use some input from a windows-savvy
reader:
http://groups.google.com/group/comp.lang.tcl/browse_frm/thread/b2170061f9a2edfb - Why does the interpreter created with thread::create not know about argv
and argc as i expected?
http://groups.google.com/group/comp.lang.tcl/browse_frm/thread/1fd2f8b4d4c1e6b9 - Where is RamDebugger? Can't find it here, can't find it there:
http://groups.google.com/group/comp.lang.tcl/browse_frm/thread/fb7be16910e1a7a9Current Version of RamDebugger is 5.5 it can be found at:
http://www.gidhome.com/RamDebugger/ramdebugger_toc.htmlDownload from: ftp://ftp.compassis.com/pub/ramdebugger/ as
ftp://ftp.compassis.com/pub/ramdebugger/RamDebugger5.5.kit or
ftp://ftp.compassis.com/pub/ramdebugger/RamDebugger5.5.zip - People starting with tcl/tk often ask for a GUI-Builder. Something
they know to need with other Widget-Toolkits:
http://groups.google.com/group/comp.lang.tcl/browse_frm/thread/60a5a54537a1be75 - Are there Paths beyond 255 Characters? Hitches, opinions,
religion on windows pathlength limitations:
http://sourceforge.net/mailarchive/forum.php?thread_id=9833529&forum_id=3854
http://sourceforge.net/mailarchive/forum.php?thread_id=9833535&forum_id=3854Thanks to Arjen Markus for his so-accurate summary of Wiki activity:
Let us get started with the summary rightaway!The guts of Tcl
- Traces are an intriguing mechanism, both loved
and feared and, yes, ignored. Learn more about
them at
http://wiki.tcl.tk/398 - The core team take performance seriously. Here
are results for commands related to the file system:
http://wikit.tcl.tk/10582 - ... and wise words about memory consumption can
be found at:
http://wiki.tcl.tk/14504 - A simple thing like toggling a logical/boolean
variable provokes a lot of ingenious solutions:
http://wiki.tcl.tk/4517 - The cosmetics of Tcl
Tcl warts: Would you (dis)agree? Have your own
warts? These are no warts, these are beauty
spots!
http://wiki.tcl.tk/1798Applying Tcl ...
- ... to SOAP: http://wiki.tcl.tk/15579 explains one particular design in detail.
- ... to browse help files and the like: http://wiki.tcl.tk/15569
- ... to detect the differences between files: http://wiki.tcl.tk/12803
- ... to run PHP-scripts: use PHP in the context of tclhttpd http://wiki.tcl.tk/12130
- ... to code on the clipboard: http://wiki.tcl.tk/15576
QOTW:
"Then again, if you have people writing BIND config files that
look like this, you have bigger problems than trying to parse them with
Tcl."—sage Melissa Schrumpf, in a thread that provides excellent
counsel on configuration from a Tcl perspective
http://groups.google.com/group/comp.lang.tcl/browse_thread/thread/1462b8dc8a16eec0/
"DoP: It seems unnecessary (and embarrassing) to memorialize such things
in the ChangeLog.
DKF: Instead, they get their own vanity thread on c.l.t..."
POTW:
GVI, The Graphical Voter Interface, is a GUI (Graphical User
Interface) for voting, suitable for use in private or public elections.
It can handle write-ins and multi-language elections, and it can automate
voting along party lines. GVI can be used for Condorcet Voting and
Instant Runoff Voting, which allow voters to rank the candidates in order
of preference. It can also be used for Approval Voting, which allows
voters to select more than one candidate. It can handle conventional
voting too, of course!
http://groups.google.com/group/comp.lang.tcl/browse_frm/thread/216ae46bd659d5d6
http://russp.us/GVI.htm
Active X-Controls using and providing:
http://groups.google.com/group/comp.lang.tcl/browse_frm/thread/6ac12685f4349420