|
Top Document: comp.lang.tcl Frequently Asked Questions (March 07, 2005) (1/6) Previous Document: -V- What training material is available? See reader questions & answers on this topic! - Help others by sharing your knowledge There are two alternatives for reporting bugs and problems. The first is the Usenet news group <URL: news:comp.lang.tcl >, an unmoderated Usenet newsgroup, created for the discussion of the Tcl programming language and tools that use some form of Tcl, such as the Tk toolkit for the X window system, Extended Tcl, and expect. Please note that postings of source code to <URL: news:comp.lang.tcl > does not automatically get archived anywhere (for example in <URL: http://www.neosoft.com/tcl/ > - the User Contributions archive site) - if you want your code to be available, you can take advantage of the <URL: http://www.neosoft.com/tcl > interface and add it yourself. See elsewhere in the FAQs for more details on the user contributed source code archive site. The second alternative would be to report problems, suggestions, new ideas, etc. directly to the author. To find the email address of the authors of Tcl/Tk based programs and extensions, (see "part4") and (see "part5"). Note that this does NOT apply to Tcl / Tk themselves - John has asked that you use <URL: news:comp.lang.tcl > for public communications. There is also <URL: http://www.sourceforge.net/projects/tcl/ > for reporting problems, suggesting improvements, and so on. When you report bugs, be sure you mention what hardware and operating system you are using (e.g. Pentium 100 mhz running Linux version x.y.z), what version of Tcl/Tk you are using (e.g. Tcl/Tk 8.3.2), what extensions you have added (e.g. tclX, dash, plus, itcl, tix, and blt), and any local modifications you have made. Then, provide if possible either a small piece of code, or a URL (e.g. <URL: ftp://ftp.myhost.com/some/path/ > ) to some code which demonstrates the problem. Either have the code explicitly mention "here's what I thought would happen", or in your description mention that. Also, if something used to work, mention which configuration you used. Most of all, be sure to provide an email address that is valid, and be sure to watch the Usenet newsgroups for responses, since seldom will private email be sent on a matter which likely is of public interest. On the other hand, if you DO get private email replies, remember to post a summary of what works to the group, so that future generations can benefit from your learning experience. If something in Tcl fails, don't just say "Tcl_Eval() fails" (or whatever function) but tell readers specifically what type of core dump occured, or what error codes were returned, what values were left in $errorCode and interp- >result, and so on. If you submit information about your platform, version of Tcl, and code which can easily duplicate the bug to <URL: http://www.sourceforge.net/projects/tcl/ >, it can be examined, verified, logged and possibly fixed in a future Tcl/Tk release. If you have devised a fix (commonly referred to as a patch) for any Tcl or Tk related software, be sure to notify the author of the software as well as <URL: news:comp.lang.tcl >. To report patches to the core Tcl and Tk software, access <URL: http://www.sourceforge.net/projects/tcl/ >. If you have software from which you think someone might benefit (either a program, function, extension, or simple example), or you have a document, magazine or journal article, thesis, project, or even commercial advertisement, be sure to let the appropriate people know. There are FAQ maintainers for each of these areas as well as a <URL: news:comp.lang.tcl.announce > newsgroup you can use. Source code postings of reasonable length (and reasonable has been pretty large) are acceptable, BUT postings are _not_ automatically archived on the Neosoft ftp site. It is always worthwhile to submit your contributions directly to the ftp site so more members in the future can benefit from your experience. To make announcements to the <URL: news:comp.lang.tcl.announce > newsgroup, send email with the details to <URL: mailto:tcl-announce@mitchell.org >. Also, feel free to just point us to your own ftp site or WWW site if you have one which can be used. Don't feel compelled to keep everything on one site - but feel free to ftp contributions there if you wish. ------------------------------ End of comp.lang.tcl Frequently Asked Questions (1/5) ***************************************************** -- Tcl - The glue of a new generation. <URL: http://wiki.tcl.tk/ > Larry W. Virden <mailto:lvirden@cas.org> <URL: http://www.purl.org/NET/lvirden/> Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -><- [[Send Tcl/Tk announcements to tcl-announce@mitchell.org Announcements archived at http://groups.yahoo.com/group/tcl_announce/ Send administrivia to tcl-announce-request@mitchell.org Tcl/Tk at http://tcl.tk/ ]] User Contributions:Top Document: comp.lang.tcl Frequently Asked Questions (March 07, 2005) (1/6) Previous Document: -V- What training material is available? Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Single Page [ Usenet FAQs | Web FAQs | Documents | RFC Index ] Send corrections/additions to the FAQ Maintainer: lvirden@yahoo.com (Larry W. Virden)
Last Update March 27 2014 @ 02:12 PM
|

Comment about this article, ask questions, or add new information about this topic: