On May 22, 6:32 ¨Âí¬ Òåéä Ôèïíðóïî ¼òåéä®ôèïíð®®®Àáôåâ®ãïí¾ ÷òïôåº > It doesn't really. ¨Âáô ìåáóïîìù óéíðìéóôéãáììùâù òå÷òéôéîç ôè> input code, attempting to place 'end' in the proper place based on > indentation. ¨Ââòåáëó óéìåîôìù éæ ùïèáððåî ôï íéóðìáãå ùïõò > whitespace incorrectly, placing an 'end' in the wrong place. As I said when I posted it: > It's very short, and pretty simple. I have no doubt that it > would need a lot of work to be robust. In its present form, this is not something I want to do in production code. It does however serve at least one valuable purpose: it demonstrates that the code snippet that Tony posted, that he specifically contrived as an example of a piece of Ruby code that would be utterly impossible to parse without 'end' statements, was in fact quite easily parsable.