Re: Best practices in writing functions

[Richard Kirk]

Hi.

I have also wanted a guide for writing oct-file .cpp code. Most of my 
stuff is rushed up to fulfil a particular need, and so is unlikely to be 
of use to anyone else. However, I would like to think I could write 
something that could last and be used by anyone if I needed to.

Perhaps I am going about this the wrong way. There are many ways of 
writing 'good code' and there are endless arguments about style. Perhaps 
we should have a Hall of Fame of Good Examples nominated from the 
existing database. The actual functions in the examples is not 
important, though something simple and easy to understand is better than 
something complicated, advanced, or obscure. The main thing is to have a 
neat and solid parsing of the inputs, and a helpful reaction to errors.

I have no good suggestions, but maybe someone else has.

Cheers.
Richard Kirk

--
FilmLight Ltd.          Tel: +44 (0)20 7292 0400 or 0409 224 (direct)
Artists House,          Fax: +44 (0)20 7292 0401
14-15 Manette Street
London W1D 4AP