Posted by Cameron Laird on 04/22/06 04:08

In article <gLc2g.18464$tN3.7823@newssvr27.news.prodigy.net>,
Bryan Oakley <oakley@bardo.clearlight.com> wrote:
>comp.lang.tcl wrote:
>> Sorry, I'm not new, I've been at it since 1996. Web programming that
>> is. Done TCL since 1999. I just don't have the means of testing my
>> TCL procs apart from using Wish on my very slow home PC (I use Linux at
>> work, haven't yet found an environment I can use to test TCL procs at
>> work and don't have root access to my machine even if I were to find
>> something).
>
>That's an odd statement. If you have the ability to edit and run them,
>you can test them. tcltest is 100% pure tcl. In fact, if you can run
>them via your web server, you can run tests *in* your webserver. Just
>drop the tcltest source code wherever you can access it (read: in the
>same file or directory where PROPER_CASE is defined) and off you go. Of
>course, you can also test them via tclsh if you have that available.
>
>As for testing them at home, I bet even the slowest PC you can find that
>is still running is sufficient to run tcltest for a modest number of tests.
>
>I don't mean to be telling you how to work. It's just that these errors
>were so trivial to reproduce that it seemed like a beginners mistake. No
>offense. I just didn't think you were aware of some of the options
>available to you.

[Back to original message]