How about: reading in a file (say /usr/share/dict/words) and producing a frequency count of the letters therein?
This looks like it could be alright.
Best to keep it simple, I think.
agreed,
however I think we should try to write the code in a way that demonstrates the main features of the languages.
i.e. - methods/procedures/functions and their syntax - conditional structures e.g. if, switch - data types ... complex and basic (classes?) - string handling - how external programs are run i.e. the "glue" side of things - stdin/stdout handling - file handling (reading and writing)
If all that is too much then we will probably need to agree on what we *do* cover.
(and some comments on what I might have missed or extraneously added is probably sensible.)
-- Zane Gilmore, Analyst / Programmer Information Services Section, Information Technology Dept, University of Canterbury - Te Whare Waananga o Waitaha Private Bag 4800, Christchurch New Zealand Phone +64-3-364 2987 extn 7895
