I'm going to disappoint you... there's no such thing as the perfect program. But when I'm writing an answer to a class exercise and showing a sample, I have to make sure it's to a high standard - and that means at least:
• Well commented
• Using good variable names
• Avoiding repetition of constants
Ideally, it would also be
• Robust to any incorrect inputs
• Avoids repeating code (no cut and paste!)
• Efficient in operation
But those latter three elements may require elements of coding (such as procedures and regular expressions) that I may not have taught early on.
So why isn't there a single perfect way to write a program? Consider this...
• Who is going to maintain the program? Does it need to be written for a novice maintainer using simpler structures and lots of comments, or for a an experienced Tcl coder who can easily read some of the more sophisticated regular expression syntax?
• There may be a compromise between speed of operation and ease of reading. Which should be selected?
• Should the code be strongly structured to allow code re-use, or should it be tuned to reduce dependencies on other modules and file - for safer distribution
• May you assume that it will only run on recent versions of Tcl and code using newer features, or is there a realistic chance that the code will need to be run on older systems too. Perhaps your version of Postbuilder isn't yet using Tcl version 8.5, for example
• Should I write my code so that it can all be see on a single page / projector screen by my delegates or should I spread it out so that it can be better understood later when it's posted at places like this for the benefit of people who've not been on the course?
I can't give you a [wrong/right] directive, in general term, on any of the above. But what is certainly right is to make our delegates aware of the issues so that they write their own code with a knowledge and maturity that takes such things into consideration
- with an objective of writing code efficiently, and code that's easy to use and easy to maintain thereafter.
Want so see what I mean? There's an example of a quite early answer written during class [here]
, and a later one [here]
which has common logic for user input separated out into a more robust common function loaded from [here]
. I'm not saying either is "right", but I prefer the second example because it's more forward useful, and I prefer the first example because my delegates can get to see something fairly effective early on.
Examples from the recent public Tcl Course
I ran at our training centre in Melksham. The course is a niche one, and we get delegates from far and wide (you are required to be fluent in English to attend - otherwise it's not fair on other delegates. Clearly the course was a hit... may I share a follow-up letter with you:
(written 2013-11-13, updated 2013-11-16)
|Dear Graham, |
I am already back in Turkey, comfortably and without any problems.
I send this mail to you to thak once againg for your informative training, help on other subjects (like public transport J), friendship and hospitality. I was very lucky to work with you and I thank you very much for everything.
I wish you, your family, Wellho Ltd. and Melksham the best for the following times.
Associated topics are indexed as below, or enter http://melksh.am/nnnn for individual articlesT050 - Tcl/Tk - Tcl, Tcl/Tk and Expect - General 
Still teaching Tcl in 2016? - (2016-01-06) 
Using Object Oriented Tcl and the Tk toolkit together - real life example - (2015-03-12) 
Public training courses - upcoming dates - (2015-02-21) 
Should we cover expect and/or Tk on our public Tcl courses? - (2011-05-11) 
Tcl - Some example of HOW TO in handling data files and formats - (2011-03-04) 
Tcl - a great engineering language - (2010-03-17) 
Learning to program in ... - (2009-11-15) 
Using Tcl and Expect to automate repetitive jobs - (2009-10-24) 
Tcl scripts / processes on a web server via CGI - (2009-09-27)Q101 - Object Orientation and General technical topics - Programming Principles 
What are callbacks? Why use them? An example in Python - (2016-02-11) 
Remember to ask the question before you listen for the answer - (2016-01-26) 
Hungarian, Camel, Snake and Kebab - variable naming conventions - (2016-01-03) 
Learning to program - what are algorithms and design patterns? - (2014-11-22) 
Rooms available tonight - how to code an algorithm from first principles - (2013-08-19) 
We not only teach PHP and Python - we teach good PHP and Python Practice! - (2013-06-18) 
Test Driven Development in Python - Customer Comes First - (2013-05-16) 
Seamless, integrated IT - we have a long way to go! - (2013-04-11) 
Web and console - same principle, same code - Ruby example - (2013-02-14) 
Lesson 1 in programing - write clean, reuseable and maintainable tidy code - (2012-12-16) 
Storing your intermediate data - what format should you you choose? - (2012-11-20) 
From Structured to Object Oriented Programming. - (2012-10-02) 
Object oriented or structured - a comparison in Python. Also writing clean regular expressions - (2012-03-26) 
Some terms used in programming (Biased towards Python) - (2011-12-12) 
Dark mornings, dog update, and Python and Lua courses before Christmas - (2011-12-10) 
What order are operations performed in, in a Perl expression? - (2011-12-07) 
Stepping stones - early coding, and writing re-usable code quickly - (2011-09-24) 
Coding efficiency - do not repeat yourself! - (2010-11-02) 
An introduction to file handling in programs - buffering, standard in and out, and file handles - (2010-09-21) 
Looking up a value by key - associative arrays / Hashes / Dictionaries - (2010-08-11) 
Program for reliability and efficiency - do not duplicate, but rather share and re-use - (2010-07-19) 
Easy - but for whom? - (2010-05-18) 
Improving your function calls (APIs) - General and PHP - (2010-04-24) 
And and Or illustrated by locks - (2010-01-17) 
Do not copy and paste code - there are much better ways - (2009-12-26) 
The music of the stock market - (2009-11-22) 
Variable names like i and j - why? - (2009-09-22) 
Planning! - (2009-08-08) 
Learning to write high quality code in Lua - (2009-07-30) 
Where do I start when writing a program? - (2009-06-11) 
Pre and post increment - the ++ operator - (2009-02-03) 
I have not programmed before, and need to learn - (2009-01-19)
Some other Articles
If elif elif elif - multiway selection in PythonLists in Tcl - fundamentals in a commented source code exampleTcl + Tk (Wish) - an introduction and revision exampleException handling in TclWriting the perfect program in Tcl?Regular Expression Substitution - TclWith the Shpigs and DonkeysA weekend away - Four in a Bed returns to Happy Donkey HillExcellent Railfuture conference, but some setup lessonsLooking to the future at Melksham Station