Re: This sort of thing might push me to Scala

Of all your points I like number 5 best. However, my
runWithWaitCursor() approach is simple and direct and, most
importantly, I know how to do that without putting a lot of effort
into working things out. I am not sure how I would detect a busy
program? How would you do that?

Many thanks for points 1 through 4. It is our coding policy that
insists on the way the code is written., It is designed to make things
clearer by keeping them separated by white space. However,  it does
tend to inflate the line count a bit. In most other situation is gives
us very clean code to look at.

But that is our POV and your may well differ.

regards,

Gordon

2009/12/18 Mathieu Bouchard <matju-i8w/[email protected]>:
> On Fri, 18 Dec 2009, Gordon Milne wrote:
>
>> How many lines of code did I just save?
>
> 1. the amount of nesting that java requires punishes you for
>    trying to pass code as a parameter
>
> 2. your newline placement punishes nesting
>
> 3. your way of counting the amount of code doubly punishes trying to pass
>    code as a parameter because (1) and (2)
>
> 4. java's lack of macros punishes anyone trying to write what they really
>    mean
>
> 5. if you had a system that automatically looked at whether your program
>    is busy and changed the cursor accordingly, there wouldn't be any
>    problem and you would never get bugs related to whether you should
>    or shouldn't use runWithWaitCursor in a specific situation
>
>  _ _ __ ___ _____ ________ _____________ _____________________ ...
> | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>