From: "Randy W. Sims" <ml-ruby@...>
Date: 2004-10-12T12:46:38+09:00
Subject: Re: Ruby Directions (was Re: quality of error messages)

On 10/11/2004 11:38 PM, Markus wrote:
> On Mon, 2004-10-11 at 18:18, Austin Ziegler wrote:
> 
>>On Tue, 12 Oct 2004 09:21:16 +0900, Hal Fulton <hal9000@hypermetrics.com> wrote:
>>
>>>Austin Ziegler wrote:
>>>I sympathize with both sides. Like you, I "flush left" my debug lines
>>>(fighting vim to do so, and hating the idea of coding without being
>>>able to do such).
>>>
>>>I typically don't leave those in long, however. YMMV.
>>
>>Me, either.
>>
>>I think that there are possibilities here, though, now that it's been
>>explained that this is something to show up only in an error
>>condition.
> 
> 
>      I will try and make it more useful; do you by any chance have a
> feeling of how/when you write flush-left code?  I am already ignoring
> comment lines, since many people write them flush left.  Do you
> generally only do one line this way?  Are they generally print/puts/p
> statements?  
> 
>      In other words, is there anything that could be simply detected
> (because I would like the code to remain small, fast, and simple) that
> would let me detect what you do as "normal" and not consider it for
> mention in the diagnostic message?

I do this also. Basically, anything not an end marker that is _flush_ 
left can be ignored for the purpose of "finding the end".

Randy.

PS: I still like the other idea (end [(module|class|def) [<NAME>]]) 
better. =)