Warp wrote:
> 1) If you ever get the temptation of using the keyword 'new', don't.
>    (And no, "malloc()" is not good either. See rule 3.)

	Out of curiosity, how realistic is that? Can you give a scenario where 
one *should* use new? (i.e. can't find a way around it).

> 2) If possible, avoid using pointers.

	As in, use references instead?

> 3) If possible, avoid functions in the C standard library.

	Amen.


-- 
Lisa: Oedipus killed his father and married his mother.
Homer: Who payed for THAT wedding?


                     /\  /\               /\  /
                    /  \/  \ u e e n     /  \/  a w a z
                        >>>>>>mue### [at] nawazorg<<<<<<
                                    anl

Post a reply to this message