You are not logged in.
In a Stack Overflow question, someone asked about some nested procedure call he found out. That is, a procedure inside another procedure.
He found out this coding style to be messy, which sounds like a reasonable opinion. But his alternative proposal of putting the internal procedure outside the main one, i.e. making it global, is IMHO even worse.
In some case, a private class, or even record or object with methods is an handy and maintainable implementation pattern.
Comments for http://blog.synopse.info/post/2012/05/2 … te-objects
Offline